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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the tool processes all pages and costs $0.03 USDC via x402, which is important context beyond the schema, but it omits return format, payment/auth details, error behavior, and whether extraction is reversible or cached.

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 is two short sentences with no wasted words, and the core scope is front-loaded ahead of the cost note. Its brevity is appropriate structurally, even though the content is under-specified.

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 paid document-extraction tool with no annotations and no output schema, the description is too thin. An agent still lacks the expected return type, the difference from preview_document, and practical details about the x402 payment requirement.

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 67%, and the description adds no parameter-level meaning. It does not clarify the relationship between url and file_base64, does not explain how 'type' or 'auto' affects extraction, and does not note that all parameters are optional.

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 description states 'Full extraction of all pages,' which conveys a verb and scope, but it never says what is extracted (text, fields, structured data) or how it differs from sibling tools such as preview_document and spread_bank_statement. The purpose is inferable but not sharply 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?

The description gives no explicit guidance on when to choose this tool over preview_document or spread_bank_statement, nor does it state prerequisites or when-not-to-use conditions. The only guidance is the implied contrast between 'full extraction' and a preview tool, which is not enough.

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