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

readOnlyHint=true already declares this as a safe read, so the bar is low, and the description adds useful behavioral context by naming the return formats (APA text + BibTeX). It does not say what happens with an unknown slug or whether one or both formats are always returned.

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?

One sentence, front-loaded with the verb and the output formats, with no filler. Every clause carries information.

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?

For a one-parameter read-only tool with no output schema, the description carries the return-value burden well by naming both formats; the remaining gap is the unexplained slug, which an agent may not know how to source.

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?

The single required 'slug' parameter has 0% schema description coverage and the description never explains what a slug is or how to obtain one; 'for a World Innovation paper' only loosely implies it identifies the paper. The description does not compensate for the schema gap.

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 ('Get') and resource ('citation') and the concrete output formats ('APA-style text and BibTeX'), scoped to World Innovation papers. It is clearly distinct from get_paper/search_papers/verify_paper by the word 'citation', 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 only implied: 'Get a ready-to-use citation' tells the agent to call it when a formatted reference is needed, but it never says when to prefer get_paper vs cite_paper or states any preconditions such as the paper needing to exist. No exclusions or alternatives are given despite three siblings.

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