convert_folder_to_markdown

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

There are no annotations, so the description carries the behavioral burden. It does disclose that the tool returns a summary of what succeeded, implying partial failures are possible. However, it does not mention overwrite behavior, directory creation, or what happens with unsupported files, which would be useful for a write operation.

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 short sentences deliver the core behavior and usage condition with no filler. The key distinguishing fact (batch conversion) is front-loaded, and every word earns its place.

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 simple two-parameter tool with fully described schema and no nested objects or output schema, the description is largely sufficient. It covers what the tool does, when to use it, and the nature of the return value, although details like output naming or conflict handling are absent.

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 100%, so both parameters ('paths' and 'output_directory') are already well documented. The description adds little parameter-level meaning beyond the schema, which is acceptable because the schema does the heavy lifting.

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 states a specific verb ('convert'), a resource scope ('several documents at once'), and an outcome (returns a summary of what succeeded). It also distinguishes itself from the single-file sibling tool by explicitly framing this as the batch variant.

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 an explicit trigger: use when the user points at a set of files rather than one. It provides a clear when-to-use signal and implicitly excludes single-file use, though it does not name the alternative tool directly.

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