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

Annotations declare readOnlyHint=true and idempotentHint=true, which the first sentence supports, but the description then details accepted upload payloads, the 256 KiB MCP transport limit, per-file quote charges, and spending authorization — implying this tool accepts documents and triggers charges. The genuinely useful disclosures (a repeated authorization reuses the account's right for the source hash; processing continues without an open browser) are buried and appear to describe a different operation.

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?

A dense, run-on block that front-loads nothing useful and interleaves format specs, billing rules, transport limits and authorization policy. Sentences do not earn their place relative to the tool's actual read-only scope, and the actionable parts are scattered rather than ordered.

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 say what 'quote and saved conversion state' contains (status, price, page count, expiry, etc.). Instead it spends its length on upload mechanics, leaving an agent unable to predict what a successful call returns or what a quote object looks like.

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 base_id and conversion_id ('64-character ID returned by the API') are already documented. The description adds no syntax, format or constraint detail for either parameter, so the baseline of 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?

The opening ('Read the quote and saved conversion state. Optional account document conversion.') gestures at reading conversion state, but the bulk of the description covers how to upload PDF/DOC/DOCX bodies, MIME types, size caps and page limits — behavior that belongs to a quoting/upload tool, not a get. An agent reading this cannot tell whether get_base_conversion retrieves an existing quote/state or performs an upload.

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?

There are scattered directives ('Check conversion_limits in get_base before upload', 'prefer raw HTTP for large files', 'Publication remains a separate action') that touch siblings such as authorize_base_conversion and publish_base, but no statement of when to call this tool versus list_base_conversions, get_base, or quote_base_document. The guidance is about the surrounding conversion workflow rather than about selecting this tool.

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