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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: edges are directional (citing → cited) while traversal is bidirectional, and hop counts land in provenance.hops. It stops short of noting path explosion, timeouts, or result caps for extended mode.

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?

Three compact sentences, front-loaded with the core action, then output shape, then the one optional flag, closing with the motivating use case. No sentence is redundant.

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?

With an output schema present, return values need not be spelled out, and the annotations carry the safety profile, so the description covers what remains: directionality semantics and the extended flag's effect. Minor gaps around performance/limits in extended mode keep it from a 5.

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 baseline is 3. The description restates the accepted identifier formats already documented in the schema, but does add meaning for extended by specifying the target ('aiming for at least 5' longer paths), which is more concrete than the schema's 'Also return longer paths.'

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 and resource — 'Find citation paths between two papers' — and clarifies the semantic model ('treating each citation as a link in either direction') plus the practical payoff ('shows how two lines of work relate'). It is clear on its own, though it never names the adjacent siblings (query_citation_graph, explore_citation_network) to draw the boundary explicitly.

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?

Usage is implied rather than stated: the reader infers this is for pairwise connectivity questions and that extended=true is for weakly connected works. There is no explicit when-not-to-use guidance or pointer to the sibling graph tools, which matters given query_citation_graph and explore_citation_network overlap in territory.

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