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

Annotations declare readOnlyHint=true and destructiveHint=false, but the description describes uploading, authorizing credit spending, and processing a document conversion. That describes write/mutating behavior and directly conflicts with the read-only annotation.

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 description opens with the list purpose but then becomes a long, disorganized block of upload, HTTP MIME type, pricing, and authorization details that do not belong to a read-only listing tool. Most sentences do not earn their place for this operation.

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 simple one-parameter listing tool with no output schema, the description should explain what conversions are returned or how to use the listing. Instead, it is dominated by irrelevant upload and quote-authorization details and never describes the listing result.

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% for the single base_id parameter, and the schema already explains it is the 64-character ID returned by the API. The description adds no further meaning about base_id, so the high-coverage 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 first clause states 'List saved conversions in your base,' but the remaining text describes uploading and converting documents, obtaining quotes, authorizing payment, and publication. This muddles the purpose and does not distinguish the tool from siblings like get_base_conversion or remove_base_conversion.

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 usage instructions concern checking conversion_limits in get_base before upload, preferring raw HTTP for large files, and authorizing a quote. These apply to an upload workflow, not to listing saved conversions, so the guidance is misleading for this read-only tool.

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