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

Annotations only cover readOnlyHint and openWorldHint, so the description earns credit for disclosing the payment model — $0.012 USDC per call via x402 — which is exactly the kind of cost/auth constraint annotations don't express. It stops short of mentioning failure modes or that input must be a URL or base64 payload, but the paid-call disclosure is real added value.

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 dense sentences that front-load the core capability before the format list and pricing. The format list is long but functional; nothing is padded or redundant.

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 no output schema, the description should ideally say what comes back (base64 vs binary vs share links), but the schema's format/store descriptions cover that, and the conversion matrix plus pricing make the tool callable. Only the input-source duality (url vs file_base64) and 20 MB cap are left to the schema.

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 already documents every parameter including the 'to' format list, store surcharge, and format=binary. The description's format enumeration duplicates the schema rather than adding syntax or constraints, so the 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 (Convert) plus the resource scope (office documents via LibreOffice) and enumerates the supported source and target formats, so the tool's remit is unambiguous. It does not, however, explicitly distinguish itself from nearby siblings like doc_convert, convert, or media_convert, leaving the boundary to inference.

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 a useful default ('to PDF (default)') and the conversion matrix, which implies when the tool applies, but it never states when to pick this over doc_convert or convert, nor any prerequisite beyond the implied x402 payment. Usage is inferable rather than explicit.

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