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

Annotations only declare readOnlyHint=false, idempotentHint=false, destructiveHint=false; the description goes well beyond them with size limits (8 MiB), page limits (200 physical pages), the MCP 256 KiB request cap, the pricing endpoint, and the note that DOC/DOCX charge once per file with pages=0. It also discloses that repeated authorization reuses the account's right for the source hash and that processing continues without an open browser. That is rich behavioral context an agent cannot get from structured fields.

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 purpose is front-loaded in the first sentence, but the rest is a dense run-on sequence mixing limits, pricing URLs, authorization policy and transport notes with no grouping. Every fact is relevant, yet the structure makes it harder to scan than it should be.

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 3-required-param mutation tool with no output schema, the description covers prerequisites, limits, pricing source, authorization and publication boundaries well. The notable gap is that it never says what a quote response contains, which matters since there is no output schema to fall back on.

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 roles of base_id, filename and file_base64 are already documented, and the baseline would be 3. The description adds transport meaning for file_base64 by explaining the raw HTTP alternative with URL-encoded X-Document-Name, which helps the agent pick the right parameter strategy for large files.

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?

Opens with a specific verb and resource: 'Upload PDF, DOCX or DOC and get its conversion quote.' An agent can distinguish this from authorize_base_conversion and add_base_document. It stops short of explicitly naming the sibling tools it must not be confused with, so it is clear but not fully differentiated.

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?

Gives prerequisites ('Check conversion_limits in get_base before upload'), scope limits ('Upload only obtains a quote'), the downstream step ('Authorize with the exact quote and explicit user authority to spend credit'), and the terminal boundary ('Publication remains a separate action'). It also routes between transports ('prefer raw HTTP for large files'). This is explicit when/when-not guidance with named alternatives.

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