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

Annotations declare readOnlyHint=true, and the description aligns by saying it 'Returns the labeled path or reports they're unconnected' — a read-only explanation operation. It adds useful behavioral context: it returns the shortest chain, reports unconnected cases, and explains how user-supplied metadata nodes behave. It doesn't mention performance or limits, but for a read-only graph query the description covers the key behavior.

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?

The description is dense but well-organized: it starts with the core purpose, then gives the node-id format, then explains special node types. Every sentence adds useful information. It's longer than average, but the complexity of the node-id system justifies the length. Could be slightly tightened, but no wasted sentences.

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 graph query with no output schema, the description covers the essential context: what the tool does, how to format node ids, how special metadata nodes work, and what the return is (labeled path or unconnected report). It doesn't explain edge_types semantics in detail, but the enum values are self-explanatory and the schema documents them. The description is complete enough for an agent to call this tool correctly.

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 coverage is 100%, so the schema already documents all three parameters. The description adds significant value by explaining the node-id format ('<type>:<key>') with concrete examples and how bare recipe ids auto-resolve. It also explains the semantics of special node types like 'tag:', 'property:', and 'component:' — meaning beyond the schema's terse descriptions.

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?

The description opens with a specific verb ('Explain HOW') and a precise resource ('the shortest chain of relationships between any two nodes'), then gives concrete examples of node pairs. It clearly distinguishes itself from sibling tools like traverse_graph by focusing on shortest-path explanation rather than general traversal.

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?

The description gives rich context on when to use the tool: to explain relationships between any two archive entities, with examples like 'what else uses this sauce?' It doesn't explicitly name alternatives or exclusions, but the node-id format guidance and relationship examples make the intended use clear. It could be stronger by explicitly contrasting with traverse_graph.

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