convert_to_markdown

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

With no annotations, the description carries the full burden. It discloses the side effect: 'Creates task and polls MinerU API,' and explains auto-configuration of model and OCR. It does not mention auth needs or rate limits, but for a conversion tool this is acceptable and adds significant value beyond the schema.

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 concise with three brief sentences and front-loaded key information. Every sentence adds value: purpose, steps, constraints, side effect, and use case. No wasted words.

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?

Given no output schema and 4 params, the description explains the conversion process and what the tool returns (download link). It covers supported formats, auto-configuration, and side effects. It could explicitly state that it combines create and poll steps, but 'one-step' and 'Creates task and polls' imply that.

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 baseline is 3. The description does not add new semantic meaning to parameters beyond what the schema already provides. It mentions auto-configuration, which relates to model_version, but does not enhance understanding of poll_interval or max_wait_seconds.

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: 'One-step document conversion' with explicit steps: 'Submit URL, poll until done, return download link.' It distinguishes from siblings like convert_pdf_to_markdown by being a general converter supporting multiple formats (PDF, DOC, DOCX, etc.) and being 'quick conversion.'

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?

It says 'Use for quick conversion' and lists supported formats, giving context for when to use it. However, it does not explicitly mention when not to use it or provide alternatives to siblings like create_parse_task or download_result. The guidance is implied but not thorough.

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