Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds one genuine behavioral trait — that output is privacy-filtered — which is useful, but says nothing about return shape, latency, or whether missing nodes error or return empty.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tight sentence with no filler and the key qualifier front-loaded. It is efficient, though arguably too terse given the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only lookup with full annotation coverage and a fully documented schema, the description is minimally sufficient. It is missing what an 'explanation' actually contains and how it relates to the published graph, which would help an agent decide whether this is the right tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; the schema already explains nodeId and projectId (including how to discover them). The description adds no parameter-level meaning of its own beyond the 'privacy-filtered' framing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Read') and resource ('hosted request node explanation'), and the qualifier 'privacy-filtered project metadata' distinguishes it from a raw graph read. It does not, however, differentiate itself explicitly from sibling read tools such as get_graph_wiki or graph_read.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no prerequisites, and no mention of alternatives. The schema hints that nodeId discovery should go through get_roots/get_graph_scope, but that routing lives in the schema, not the description, and the description itself offers no invocation context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.