format_bibtex

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

With no annotations present, the description carries the full burden of explaining behavior. It states that a standardized BibTeX entry is generated, but it does not disclose output format, citation-key behavior, handling of missing optional fields, or any validation/error behavior.

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 a single, front-loaded sentence with no wasted words. It communicates the core action and the key inputs immediately.

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 adequate for a straightforward formatting tool, and the schema covers all parameters. However, with no output schema and no annotations, it would benefit from describing the returned BibTeX format and clarifying optional DOI behavior, so an agent is not left guessing.

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 schema already describes all parameters, so the baseline is 3, but the description introduces ambiguity by listing DOI as an input even though it is optional in the schema, while omitting URL entirely. This can mislead the agent into treating DOI as required.

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 ('Generates') and resource ('standardized BibTeX entry'), and lists the required inputs. This clearly distinguishes it from sibling tools like verify_citation and search_academic_papers, which serve different purposes.

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?

No guidance is provided about when to use this tool versus the alternatives. The description implies use for generating BibTeX, but it never mentions conditions, exclusions, or how it relates to verify_citation or search_academic_papers.

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