Save Bibtex

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

The description adds 'atomically' to indicate all-or-nothing writes beyond the annotations' destructiveHint. It also discloses deployment-specific path constraints (local stdio full access, HTTP confined root). No contradiction with annotations; the description enriches the behavioral profile.

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 sentences with no redundancy. The main action is stated first, followed by a deployment constraint. Every word contributes value.

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?

Despite having an output schema, the description omits critical details for a mutation/destructive tool: what the parameters mean, whether existing files are overwritten, error handling, and interaction with collection/items. An agent cannot confidently invoke this tool without further clarification.

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 0%, so the description must compensate for parameter meaning. It only hints at 'BibTeX or BibLaTeX' (covering biblatex) and 'local file' (save_path), but leaves item_keys, collection_id, and include_abstract unexplained. The parameter names are not self-evident enough for reliable use.

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 the action ('Export BibTeX or BibLaTeX and atomically write it to a local file') with a specific verb, resource, and destination. This distinguishes it from siblings like get_bibtex (which likely returns text) and save_pdf (which saves a different format).

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 usage when a local file is needed, but it does not explicitly state when to prefer this over get_bibtex or other alternatives. The deployment note about local stdio and HTTP confined file roots provides operational context but no direct tool-selection guidance.

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