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

No annotations are provided, so the description carries the full behavioral burden. It does disclose one concrete trait — a 2-credit cost — which is real value beyond the schema, but it says nothing about permissions, limits, failure modes, or what a successful conversion returns.

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, front-loaded with the core action and followed by the cost. Every sentence earns its place with no filler.

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 3-parameter conversion tool with no annotations and no output schema, the description covers what it does and its cost but omits anything about the return value (URL, binary, file handle) or error behavior. Given the schema handles parameters well, this is adequate but leaves an obvious gap around output.

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 the schema fully documents file_url, source_format (with its enumerated values) and target_format (with default and ConvertAPI fallback). The description adds no parameter-level meaning beyond restating the resource categories, so the baseline 3 is appropriate.

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?

States a specific verb+resource ('Convert documents, web pages, spreadsheets and images between formats') and names the input categories, which is precise enough to distinguish it from the sibling tools (none of which is a format converter). It stops short of 5 because it doesn't explicitly contrast itself with adjacent siblings like images or screenshot.

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 no when-to-use/when-not guidance and names no alternatives. An agent must infer from the sibling list that no other conversion tool exists. The only usage-adjacent content (the ConvertAPI routing note) lives in the schema, not the description.

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