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

Annotations already declare readOnlyHint=true, and the description adds critical async behavior and result format. No contradictions. It could mention rate limits or concurrency, but for a read-only async tool, this is sufficient.

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 concise sentences that front-load the main action and then provide essential async workflow details. No wasted words.

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 explains the result contains matches with positions. It covers the async flow (polling vs callback). Could mention that the job ID is returned in the response, but overall complete for a tool with 5 fully documented parameters.

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 description adds little parameter-specific meaning beyond the schema. It mentions async behavior generally but does not elaborate on parameter usage beyond the schema's own descriptions.

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?

Description clearly states 'OCR a scanned PDF and search for text in it', which is a specific verb+resource combination. It distinguishes from sibling tools like 'search-pdf-content' by explicitly mentioning OCR and async behavior.

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?

Explicitly states the tool runs asynchronously, provides polling via 'check-job-status' or a callback via 'webhook_url', and describes the result content. However, it does not explicitly state when to use this tool over 'search-pdf-content' (non-OCR) or other search tools.

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