citations

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

With no annotations, the description carries the full burden and does disclose data egress (paper keys and search queries to the Reviewer Zero index, per-key request counting, nothing stored). It does not describe output/pagination behavior beyond the limit range, and a large share of the privacy text concerns other tools (review_paper, check_citations) rather than this one.

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 functional sentences are tight and front-loaded, but the privacy block is long and much of it is off-topic for this tool (it explains what happens when calling review_paper and check_citations). That dilutes the signal for an agent trying to select this tool.

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?

An output schema exists, so return values need no explanation. Function, direction semantics, and limit bounds are all covered. The only real gap is the meaning of the required `key` parameter, which is left implicit.

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 0%, so the description must compensate, and it does: it defines both directions and gives the limit range (1–200, default 50). The `key` parameter is not explicitly defined, though the surrounding text implies it is a paper key.

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 gives a specific verb (list) and resource (papers a paper cites / papers that cite it), and it disambiguates the two directions using the exact enum values. An agent can tell this apart from find_prior_work or paper without opening the schema.

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 states a concrete workflow: 'follow a candidate from find_prior_work one hop,' naming the sibling that leads into it. There is no explicit when-not guidance or statement of when the other direction is preferred, so it falls short of a 5.

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