generate_citations

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

The description discloses the multi-step behavior: resolving via Semantic Scholar, optionally enriching with OpenAlex, and outputting to three formats. This adds meaningful context beyond the readOnly/destructive annotations, though it does not discuss failure behavior or edge cases.

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 compact sentences, front-loaded with the primary action, and each clause contributes meaningful detail (resolution, enrichment, output formats). No redundancy or 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?

Given the three parameters, annotations, and presence of an output schema, the description covers the main workflow and outputs. It omits edge-case handling, but that is not required for a tool of this complexity.

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?

All three parameters are fully described in the input schema (100% coverage), so the description's brief mention of resolution, enrichment, and formatting adds little new parameter-level detail. Baseline 3 is appropriate when schema carries the parameter documentation burden.

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 uses a specific verb 'Generate' and a clear object 'formatted citations for one or more papers,' and elaborates with supported formats and enrichment workflow. This clearly distinguishes it from sibling tools like get_citations, which would retrieve citation lists rather than format references.

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 implies the use case of converting paper identifiers into formatted reference strings, with the output formats making the context clear. It does not explicitly exclude alternatives or say 'use when you need BibTeX/CSL-JSON/RIS,' but the purpose is unambiguous enough to guide selection.

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