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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the accepted ref forms and the formatting styles, which is modest but real context beyond the annotations, and nothing about auth or limits is needed for a pure read.

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?

Two short sentences, front-loaded with what the tool returns, followed by the input format. No filler.

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 structure need not be described, and the input forms and styles are covered. The only gap is the absence of when-to-use guidance relative to the many sibling read tools, which is minor for such a simple, deterministic operation.

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 the baseline would be 3, but the description goes further by showing three accepted ref shapes ("196:2.1", "1:196.2.1", "196.2.1") where the schema only illustrates one, adding genuine format guidance for the required parameter.

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+resource: produces a formatted citation of one paragraph, and names the four supported styles. It is clearly distinguishable from siblings like paragraphs.get or quotes.verify, though it does not explicitly contrast itself against any of them.

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?

The description never states when to choose this tool versus paragraphs.get or quotes.verify, nor any prerequisites (an existing ref, a paper lookup). Usage is only implied by the name and the mention of citation styles.

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