apply_manuscript_format

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

With no annotations provided, the description carries the behavioral burden, and it does so well: it discloses auto-backup behavior, atomic validated save, refusal of documents open in Word, and that contested elements are itemized in not_applied. Minor ambiguities like the meaning of 'flagged' and the 'All three' count prevent a perfect score.

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 dense but efficient, front-loading the purpose before diving into style specifics, exclusions, and operational details. It could be better structured with bullets, and the 'All three' inconsistency slightly mars readability, but every sentence contributes substantive 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?

For a complex tool, the description is quite complete: it covers supported styles, style-specific formatting rules, refusal conditions, backup behavior, and save guarantees. Since an output schema exists, return values don't need description. Remaining gaps such as the meaning of 'flagged' and how the reference list is found keep it from a 5.

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. It adds rich meaning for 'style' and useful context for 'running_head' and 'author_last_name', but 'backup=False skips rotation only' is ambiguous about whether backup is disabled entirely, and 'file_path' is never mentioned. The compensation is partial, not complete.

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 opens with a specific verb and resource: 'Apply a style's page-level manuscript conventions,' and then enumerates exactly which styles are supported (apa7, apa7-professional, mla9, chicago17). This clearly distinguishes it from generic tools like apply_style or apply_template, which do not target page-level manuscript conventions.

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-not conditions: it refuses IEEE/Vancouver/ASA/Harvard formats and states that contested items are not applied. However, it does not name alternative tools for cases where this tool should not be used (e.g., apply_style, set_paragraph_format), so it stops short of full alternative routing.

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