convert_document

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

With no annotations, the description must carry the full behavioral disclosure burden. It reveals that the tool dispatches to other conversion tools and preserves output-path containment, which is useful, but it does not disclose operational behavior such as async execution, mode handling, side effects, failure behavior, or security implications.

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 short and free of fluff, with each sentence carrying some information. However, it is under-specified for a 7-parameter entrypoint tool, so its brevity is more a sign of incompleteness than effective conciseness.

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?

This tool has 7 parameters, no annotations, and no output schema, making it a relatively complex tool. The description only covers the routing and output-path containment concept; it omits conversion behavior, parameter semantics, async behavior, source/target format handling, and return values, leaving the AI agent without enough information for correct invocation.

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% and the description adds no parameter-level meaning. All seven parameters (`mode`, `source`, `md_text`, `async_mode`, `output_path`, `source_format`, `target_format`) are left entirely reliant on their names, with no guidance on formats, defaults, relationships, or required values beyond the required flags.

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 identifies this as a 'Consolidated document conversion entrypoint' that 'dispatches to the existing conversion tools', so the core purpose of converting documents is clear. However, it does not mention a specific conversion verb/resource or name the underlying tools, leaving the actual scope vague relative to the many conversion-related siblings.

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 phrase 'Consolidated ... entrypoint' implies this should be used as a routing tool for document conversion, and the mention of 'output-path containment policy' provides some contextual guidance. But there is no explicit statement of when to prefer this over the sibling conversion tools, no negative cases, and no alternatives named.

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