convert_markup

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It does not state whether the tool writes output files, requires specific dependencies, or if it is a read-only operation on the input. The description only lists formats, leaving behavioral traits undefined.

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, concise sentence that front-loads the tool's core purpose. It avoids redundancy and is easy to parse. However, it is under-specified, which detracts slightly from appropriateness but not from 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 is a complex tool with multiple formats, options, and possible outputs, yet the description provides minimal contextual guidance. It does not explain the conversion direction, output path behavior, or typical use cases. The schema covers structure but not usage context, so the description is insufficient for correct invocation in many scenarios.

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 75%, which is high, so the schema already documents most parameters. The description adds no parameter details beyond that, so it does not compensate for any gaps, but it is not required to either. This meets the baseline for high coverage.

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' and a specific resource 'markup/text formats' listing many formats. However, it does not mention the output formats or differentiate itself from sibling tools like convert_document, convert_ebook, or convert_pdf, making its scope ambiguous.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention that this is for markup/text files specifically, nor exclude other conversion tools. The agent would have to infer usage from the format list.

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