query/explain and the serve MCP tools don't surface node.description / community_name from graph.json #3026

Version: graphify 0.17.1

Summary
After the description pipeline populates node.description and community_name in graph.json, the live query surfaces don't expose those fields — only the export wiki / export obsidian / static studio paths render them. This means anything built on the query path can't see the descriptions that are already in the graph.

What I observed

• graphify query and graphify explain print the structural fields (label, file, degree, community id) but not node.description, and print the raw community N rather than the resolved community_name.
• Against graphify serve (MCP), across query_graph, get_node, get_neighbors, get_community, first_hop_summary, god_nodes, review_analysis, graph_stats: none return node.description. Only get_node includes the resolved community_name (e.g. Community: 2 (Services)); the other tools show the generic Community N.

Reproduce

1. Run the describe pipeline so graph.json has non-null node.description and named communities.
2. graphify query "<something>" / graphify explain <node> → no description in the output.
3. Start graphify serve, call any tool → no description field in the payload.

Request
Have the live query surfaces render the fields that already exist in graph.json:

• query / explain text output include node.description and the resolved community_name.
• The serve MCP tools include description (and community_name consistently) in their payloads.

These are already populated in the graph; this is about exposing them on the consumption path, not computing anything new.