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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered structurally. The description adds no removal-specific behavior at all — nothing about whether the released base slot is immediately reusable, whether removal is reversible, or what happens to an already-authorized conversion — while instead disclosing unrelated upload, credit-charging and page-count behavior.

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 relevant content is one sentence; the remaining bulk is copy-pasted upload/pricing/publication prose that has no bearing on removing a conversion. It is front-loaded, but nearly every following sentence fails to earn its place and actively misdirects.

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?

A simple 2-parameter destructive operation with full schema coverage shouldn't need much, but an agent still needs to know the effect of removal and its relationship to authorize_base_conversion/get_base_conversion. Instead the description spends its budget on irrelevant document-upload constraints, leaving the actual removal semantics unexplained.

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% and both required parameters (base_id, conversion_id) are documented in the schema as 64-character IDs returned by the API. The description mentions neither parameter, so it contributes nothing beyond the schema; 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?

The opening clause ('Remove an unauthorized quote and release its base slot') names a specific verb and object, which does let an agent identify the operation. But it's followed by 'Optional account document conversion' and dozens of lines describing upload, MIME types, pricing and publication that belong to a different tool, muddying what this tool actually does. It never distinguishes itself from siblings like authorize_base_conversion, get_base_conversion or list_base_conversions.

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 only guidance-adjacent phrases ('Check conversion_limits in get_base before upload', 'Authorize with the exact quote') are instructions for an upload/authorization flow, not for when to call this removal tool. Nothing states that this should be used for un-authorized quotes rather than authorize_base_conversion, nor what happens after removal.

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