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

Annotations show readOnlyHint=false and destructiveHint=false. The description adds the output (parsed JSON + verify URL) but does not clarify if state changes occur (e.g., storing extracted data). Since annotations already hint at non-read-only behavior, the description should ideally explain any side effects or stored state.

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 sentences with no filler. First sentence covers purpose and output, second provides usage guidance. Every word earns its place.

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?

Given no output schema, the description adequately mentions return values (parsed JSON + verify URL). It does not detail template-specific fields or error handling, but the tool is fairly simple with 3 params and no nested objects.

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% with each parameter described. The description adds no further parameter details beyond schema, so baseline 3 is appropriate.

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 it extracts structured data from PDFs, lists document types (invoice, receipt, contract, ID document, or any form), and mentions return values (parsed JSON plus verify URL). The verb 'extract' combined with the resource (document) is specific, and it distinguishes from siblings as the only extraction 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?

The description explicitly says 'Use this when an agent needs to read an inbound document and act on it,' providing clear context. It lacks an explicit 'when not to use' or alternatives, but no direct sibling competes for this purpose, so it's sufficient.

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