citation_graph

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing result bounding (default 50), disk caching, unauthenticated quota behavior, and the exact failure mode (status=rate_limited with a warning rather than a hard fail). This is exactly the operational context an agent needs before calling an external API.

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?

Front-loads the core purpose in sentence one, then layers in operational details. Each sentence is informative, though the API-key/rate-limit discussion is somewhat verbose for the space it occupies.

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 carries the return-value burden; it explains bounding, caching, and the rate_limited status but does not describe the result shape (how citing vs referencing papers are represented). Still, coverage is solid for a two-parameter read tool.

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 both parameters are already documented. The description reinforces the default bound of 50 and the purpose of paper_id (an arXiv paper), but adds no syntax or format detail beyond the schema; baseline 3 is appropriate.

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: returns papers citing an arXiv paper plus the papers it references, via Semantic Scholar's citation graph. This bidirectional citation-graph scope is distinguishable from search-oriented siblings like search_papers or semantic_search, though no sibling 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?

Usage is implied by the specific functionality, and it gives operational context (quota bounds, caching, when an API key helps). However, it never says when to prefer this over sibling tools such as export_citations or search_papers, leaving selection to inference.

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