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

With no annotations, the description carries the burden and does substantial work: it discloses the return value ('Returns download URL'), the cost (100 sats), the auth model (Lightning pay-per-request, no API key/account), and the create_payment prerequisite. It omits operational traits such as file-size limits, expected duration, and whether execution is synchronous or async (the resultKey retry parameter hints at timeouts but the description never states it).

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?

Capability and format coverage are front-loaded, followed by pricing and the payment prerequisite, which is the right order for an agent deciding whether to call. There is some promotional padding ('Industrial-grade conversion engine — preserves formatting and quality') and mild redundancy in 'no API key, no account, no subscription needed', but no sentence is truly wasted.

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 6-parameter, no-output-schema, no-annotation tool, the description covers the essentials: what it converts, what it returns, what it costs, and what must happen first. The remaining gap is operational behavior around long-running conversions and failures, only faintly implied by the resultKey parameter.

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 every parameter including the fileUrl/fileBase64 mutual exclusivity and the resultKey retry semantics is already documented in the schema. The description adds no format syntax guidance (e.g., accepted extension strings) beyond what the schema states, so baseline 3 applies.

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 and resource ('Convert files between 200+ formats') and enumerates concrete conversion families (PDF→JPG, MP3/WAV, MP4/AVI), so the agent knows exactly what capability this covers. It does not, however, differentiate itself from siblings that overlap in scope, notably convert_html_to_pdf, which the description implicitly claims (HTML→PDF) without saying which tool should win.

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?

Gives a clear usage context and a hard prerequisite: 'Requires create_payment with toolName=\'convert_file\'', which tells the agent the ordering of calls. It stops short of explicit exclusions or naming alternatives (e.g., convert_html_to_pdf, merge_pdfs), so the boundary with siblings is left to inference.

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