convert_markdown_batch

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

With no annotations, the description must carry full behavioral burden. It explains output naming ('Output files are named after input files and placed in the specified directory') and shared settings, but it does not address potential side effects like overwriting existing files, error handling, or whether input files are modified. This adds some context but leaves gaps.

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 two short sentences, front-loaded with the core purpose. Every sentence adds meaningful information—batch conversion, shared settings, and output naming—with no fluff or redundancy.

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 covers the main batch behavior, output naming, and shared settings, which is sufficient for a 4-parameter tool with full schema coverage and an output schema. It could be improved by mentioning whether files are processed sequentially and how errors are handled, but the core is complete.

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 coverage is 100%, so all four parameters have descriptions. The tool description mentions 'same template and format settings' which loosely ties to template_path and output_format, but it does not add significant detail beyond what the schema already provides. Baseline of 3 is appropriate.

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 tool's purpose: 'Batch convert multiple markdown files to Word/PDF.' It specifies the action, resource, and scope, and the 'batch' / 'multiple' phrasing distinguishes it from the sibling tool convert_markdown for single files.

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?

Usage is implied rather than explicitly stated. The description says 'Batch convert multiple markdown files' and mentions shared template/format settings, which suggests when to use it, but it does not explicitly say 'use this instead of convert_markdown for multiple files' or define when not to use it.

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