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

The description discloses key behavioral traits: requires payment (100 sats), returns a download URL, preserves formatting and quality. Without annotations, it carries the burden and does so adequately, though it could mention rate limits or file size constraints.

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 efficient and front-loaded with the core purpose, then lists format categories, quality, return type, and payment model. Every sentence serves a purpose, though it could be slightly more concise.

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 the tool has 5 parameters, no output schema, and no annotations, the description provides sufficient contextual completeness: it explains the payment flow, the need for 'create_payment', and the expected output (download URL). The agent can use this to correctly invoke the tool.

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?

With 100% schema coverage, baseline is 3. The description adds context about the conversion process and payment requirement but does not elaborate on parameter details beyond what the schema already provides.

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 converts files between 200+ formats, listing categories like documents, images, audio, and video. The verb 'convert' and resource 'files between 200+ formats' make the purpose specific and distinct from sibling tools like 'convert_html_to_pdf'.

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 explains the pay-per-request model with Bitcoin Lightning and explicitly mentions the prerequisite of calling 'create_payment' with toolName='convert_file'. However, it does not provide explicit when-not-to-use guidance or compare to alternatives.

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