save_draft_as_docx

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

The description adds little beyond the annotations. Annotations already indicate idempotentHint=true and destructiveHint=false, but the description does not disclose behavior like overwriting existing files, whether the source markdown is modified, or any side effects. The mention of 'pandoc' is technology detail, not 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, compact sentence with no extraneous words. It front-loads the core purpose and is appropriately minimal.

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?

With three parameters, no output schema, and minimal annotation, the description does not provide enough context for an agent to correctly invoke the tool. It omits explanations of case_folder, output_filename, and markdown_filename, and does not describe expected behavior or error conditions.

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 missing parameter meanings. It does mention 'markdown draft' and 'docx', which hints at the roles of markdown_filename and output_filename, but it does not clearly explain each parameter or their defaults. This is insufficient compensation.

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 verb 'Render' and the resource 'a markdown draft to a filing-grade docx via pandoc', which is specific and unambiguous. However, it does not explicitly differentiate itself from sibling tools like save_artifact, so it falls short of a 5.

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 on when to use this tool versus alternatives such as save_artifact or other conversion tools. The description only states what it does, leaving the agent to infer usage context on its own.

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