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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false), so the bar is lower. The description adds genuinely useful non-annotation context: the graph is hand-curated, resolves preprint-to-published duplicates that automated graphs double-count, and is authoritative for astronomy. It does not discuss rate limits or auth, but those are handled elsewhere.

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 sentences, front-loaded with the core retrieval behavior. Every sentence earns its place: what the tool returns, why the data is trustworthy, and how to use the direction parameter. No filler or repetition.

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 no output schema, the description adequately explains the return nature (papers in the citation graph) and the data's authority. Annotations cover the safety profile and the schema covers pagination, sorting, and auth via _apiKey. Missing only granular output-field detail and explicit paging behavior, which keeps 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 description coverage is 100%, so the schema already documents all six parameters, including the direction and sort enums. The description restates the direction semantics already in the schema ('citations' vs 'references') and adds only a mild reframing ('impact' vs 'lineage'). It does not add syntax or format detail beyond what the schema provides.

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 states a specific resource (the ADS citation graph) and the exact relationship it returns: papers citing a given paper or papers it cites. It is clear at a glance. However, it does not explicitly distinguish itself from sibling tools like ads_search or ads_paper, so it falls short of the sibling-differentiation bar for a 5.

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?

It gives parameter-level guidance ('direction="citations" for impact' and 'direction="references" for lineage') and implies authoritative use for citation analysis, but it never says when to choose this tool over ads_search, ads_paper, or other alternatives. No when-not or exclusion guidance is present, leaving usage implied rather than explicit.

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