convert_file

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

With no annotations, the description carries the full burden. It discloses cost (100 sats), payment flow (no API key), and output (download URL). However, it does not clarify whether conversion is synchronous or asynchronous, nor does it mention size limits, rate limits, or failure modes. This is adequate but incomplete.

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 front-loaded with the primary action and is reasonably concise. Each sentence adds information, though some phrasing ('Industrial-grade conversion engine') is slightly promotional. Overall efficient, earning a 4.

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 5 parameters and no output schema or annotations, the description covers payment and format details but omits the return value structure (e.g., exact JSON format) and does not clarify asynchronous behavior despite sibling tools like check_job_status existing. This leaves gaps, scoring a 3.

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 adds value by explaining the mutual exclusivity of fileBase64 and fileUrl ('provide this OR fileUrl'), which is not explicitly stated in the schema. This extra context justifies a 4.

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 'Convert files between 200+ formats' and lists specific categories (documents, images, audio, video), making the purpose evident. However, it does not explicitly differentiate from sibling tools like convert_html_to_pdf or merge_pdfs, which warrants a 4 rather than 5.

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 mentions the payment prerequisite ('Requires create_payment with toolName=convert_file') but offers no guidance on when to use this tool versus alternatives. It does not specify preferred use cases or exclusions, leaving agents uncertain about tool selection.

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