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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and a closed-world scope, so the safety profile is covered. The description adds the useful fidelity instruction to use the returned text as given rather than retyping it, but says nothing about failure modes when a paper or section is not found.

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 with no waste: the core action and its scope come first, followed by the practical instruction about handling the output. Nothing is repeated or padded.

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 an output schema present, the description need not explain the returned citation text, and it correctly covers the paper/page duality, the optional section scoping and the available styles. What remains thin is guidance on what happens for unmatched inputs or whether a section must be an exact heading.

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 100%, so all three parameters are already documented, including the accepted paper identifiers and the style enum. The description repeats the style list and confirms section-level scoping but adds no accepted-format or matching detail beyond the schema.

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 and resource (return an exact citation for a paper or Technical Library page) plus the output formats, which is clearly distinct from retrieval siblings like get_paper or get_technical_page. It does not explicitly name those siblings, so an agent must infer the distinction from the word 'citation'.

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 rather than stated: the agent learns this is the tool for producing references and that section-level citations are possible. There is no explicit when-to-use/when-not guidance and no named alternative for adjacent tasks such as fetching the paper itself, so the routing must be inferred.

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