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

Beyond the minimal annotation (destructiveHint: false), the description adds crucial behavioral context: async execution, job id return, and the need for polling or a webhook callback. No contradictions with annotations.

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?

Two sentences, front-loaded with purpose and behavior, zero wasted words. Highly concise.

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 2 parameters and no output schema, the description fully covers the async workflow, job id mechanism, and callback vs polling options. No gaps for an agent to act correctly.

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%, so the schema already documents both parameters. The description adds value by tying 'webhook_url' to the async callback behavior, but does not provide additional syntax or format details.

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 clearly states the tool's purpose: 'Run OCR over a scanned PDF and return a searchable PDF with embedded text.' It uses a specific verb ('Run OCR') and resource ('scanned PDF'), and effectively distinguishes it from siblings like 'read-pdf-content-with-ocr' (which returns text) and 'convert-pdf-to-image'.

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 explains that the tool runs asynchronously and returns a job id, then instructs to poll 'check-job-status' or provide 'webhook_url' for results. This provides clear usage guidance, though it lacks explicit when-not-to-use conditions.

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