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

Beyond the annotations, the description discloses the critical traits: this spends real credit, requires explicit user authority, and processing continues without an open browser (async). It also explains that a repeated authorization reuses the account's right for the same source hash — though this sits in mild tension with idempotentHint=false and could be stated more precisely.

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 core instruction is front-loaded, but roughly two-thirds of the text (MIME types, 8 MiB cap, 200-page PDF limit, 256 KiB MCP transport, base64 guidance) describes the upload/quote tool rather than authorization. This is padding that actively misdirects and should have been trimmed.

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 credit-spending mutation with no output schema, the description does cover the essentials: cost, required authority, repeat-call semantics, async continuation, and the follow-up publish step. What it lacks is any indication of what a successful authorization returns (e.g., conversion status or queued state), and the irrelevant upload detail crowds out room for that.

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 the schema already documents all four parameters, including the nested quote object, the 409-on-changed-fields rule, and that authorize must be true. The description reinforces 'authorize with the exact quote' but adds no syntax or format detail the schema lacks.

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 sentence — 'Authorize the quoted price and queue conversion' — gives a clear verb and resource. However, the bulk of the remaining text describes file upload formats, size limits, and HTTP transport constraints that belong to quote_base_document, which blurs what this tool actually does. An agent reading the full description could mistake it for an upload tool.

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 is real routing guidance: check conversion_limits via get_base first, authorize only with the exact quote and explicit user authority to spend credit, and publication remains a separate action (pointing to publish_base). But it never explicitly says 'use quote_base_document to obtain the quote first' in the description body — that only appears in the schema — and the upload-oriented guidance is misplaced here.

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