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

The description discloses key behavioral traits beyond annotations: it always runs asynchronously and returns a job id. Annotations only indicate readOnlyHint=true, so this adds significant transparency. However, it omits potential constraints like rate limits or file size limits.

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: first states purpose, second explains async usage. Extremely concise, front-loaded, and no redundant information.

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?

The description covers the core functionality, async workflow, and result retrieval. It does not detail the job status response format or limitations, but given the complexity and lack of output schema, it is reasonably complete.

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 baseline is 3. The description adds context about async behavior linking to the parameters (e.g., webhook_url for callback), but does not add substantial new meaning beyond the schema 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?

The description clearly states the action ('OCR a scanned PDF') and the outcome ('return the extracted textual content, page by page'). It distinguishes itself from siblings like 'read-pdf-content' (for text PDFs) and 'search-pdf-content-with-ocr' (for searching).

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 the async behavior and provides explicit guidance on how to obtain results: poll 'check-job-status' or use 'webhook_url'. It does not explicitly state when not to use, but sibling differentiation is implied.

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