semantic_scholar_export_citation

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

The description discloses that the return is plain text, no response_format option, and lists error conditions (unknown ID, no citation data, wrong format). Annotations already provide readOnlyHint and idempotentHint, so the description adds useful behavioral context without contradiction.

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?

The description is three sentences with a clear structure: first sentence states purpose, second gives usage context with example, third explains return format and errors. No wasted words.

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 tool's simplicity (1 required param, output schema exists), the description covers purpose, required input, output format, and error conditions. It is complete for an agent to invoke correctly.

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 input schema already describes each parameter (paper_id, format, api_key) with details, so the description adds little beyond usage context. Baseline 3 is appropriate for high schema coverage.

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 clearly states 'Export a citation for a paper in BibTeX format,' specifying the verb (export), resource (citation for a paper), and format (BibTeX). It distinguishes from sibling tools that handle searching, author details, or bulk operations.

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 explains when to use the tool (after obtaining a paper ID from semantic_scholar_search_papers or semantic_scholar_match_paper) and provides an example. It does not explicitly state when not to use it, but the context is clear given sibling tools.

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