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

Annotations already cover readOnly, idempotent, non-destructive and openWorld, so the safety profile is settled. The description adds genuinely non-obvious behavioral context: rows correspond one-to-one with API hits, and an empty result reflects an empty API response rather than proven absence of citations. It does not mention the limit cap or rate-limit 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?

Three short sentences, zero filler, with the primary purpose and the two relation modes front-loaded before the caveat.

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 shape needn't be restated, and the description goes further by explaining empty-result semantics. The main remaining gap is the absence of guidance on the limit parameter and on pagination beyond the 20-row cap.

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 carry the param burden. It explains the critical relation enum well (cited_by = papers citing the work, references = papers the work cites), but identifier and limit are left entirely to the schema, which supplies only type and bounds, no meaning.

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) plus the exact selection criterion, and it defines both relation modes (cited_by vs references) inline. It is immediately clear this is a citation-graph lookup rather than a keyword search, though no sibling tool is named 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?

It tells the agent which relation value maps to which direction of citation, which is actionable parameter-selection guidance. However, it never says when to prefer this over search_papers or get_paper, and it gives no prerequisites or exclusions.

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