Generate a bibliography from TeX

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

Annotations already convey safety/behavioral hints (idempotent, non-destructive, etc.), but the description adds no further behavioral context such as network usage or side effects. It essentially restates the tool's purpose.

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 short sentence, front-loaded with the action and result. 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?

The description is too sparse to fully guide an agent: it omits when to use the tool, what the format/detail options mean, and any behavioral notes. Despite having an output schema and annotations, the description alone leaves the agent under-informed.

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 covers only 33% of parameters (tex_source has a description), and the tool description does not explain the 'detail' or 'format' enums, leaving the agent to guess what values like 'latex_eu' or 'diagnostic' produce.

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 the specific verb 'Generate' and names the output ('BibTeX or formatted LaTeX bibliography content') and input source ('TeX citations'), clearly distinguishing it from sibling tools like export_literature.

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 tool is for converting TeX citations into a bibliography, but does not explicitly state when to choose it over alternatives like export_literature or search_literature. It provides clear input context but no exclusions.

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