convert_content

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

Annotations indicate non-readonly, non-destructive, non-idempotent, open world. Description adds cost transparency ('Flat fee $0.05 per file') and hard limit on content length. Could mention error handling or job status.

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?

Concise, well-structured with no wasted sentences. Front-loaded with purpose, then conditions, then supported formats. Uses bolded limits and alternative tool names.

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?

With 4 parameters fully covered, output schema present, and description providing cost and limits, the tool is fully documented. No missing context for an agent to use it correctly.

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%, but description adds meaning: explains content can be text or base64 depending on input format, defaults, and the 10k character limit. Only minor gap is no explicit mention of encoding default in description.

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 uses a specific verb ('offload an inline document conversion') and resource ('Botverse'), distinguishes from sibling tool convert_from_url, and clearly states the tool's function.

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?

Explicitly states when to use (self-generated content under 10,000 chars), when not to use (longer or external files), and directs to convert_from_url as alternative. Also lists supported input/output formats.

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