convert_citation_style

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

With no annotations provided, the description carries the full transparency burden and does so thoroughly. It discloses that this is a 'BETA (heuristic)' converter, that unresolved items are 'left verbatim and flagged', that dry_run leaves the file 'byte-identical', that errors leave the original untouched, and that the tool refuses documents open in Word. Backup and atomic-save behavior are also explicitly described.

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 long but appropriately dense for a complex, heuristic conversion tool. It front-loads the critical BETA warning, then covers scope, limitations, safety, backup, and exclusions in clearly separated sentences that each add actionable information.

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 complexity, the lack of annotations, and the sparse schema, the description is remarkably complete. It covers supported conversions, what gets flagged, field-based exclusions, prerequisite detections, dry-run/backup/error safety, and open-document refusal. The presence of an output schema means the absence of a detailed return-value explanation is acceptable.

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 compensates by enumerating valid target styles, explaining dry_run behavior, and detailing backup semantics. However, it never explicitly names or documents the source_style parameter or its accepted values, leaving that somewhat to inference from default 'auto' and the conversion-direction examples.

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 and resource: 'Convert a manuscript's PLAIN-TEXT citations and reference list to a target publication style', and enumerates exact style names. It also distinguishes itself from nearby siblings by stating that citation FIELDS are 'routed away' to set_bibliography_style and that parse_references is the read-only stage 1.

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 gives explicit when-to-use guidance: this is for plain-text citations and reference lists needing style conversion. It also names alternatives and exclusions: Word-native or Zotero/Mendeley/EndNote fields should go to set_bibliography_style or be restyled in the manager, and detect_citation_system should be run first on unfamiliar documents.

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