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

Annotations are minimal (only destructiveHint: false), so the description carries the burden. It discloses that the tool always runs asynchronously and returns a job ID, which is critical behavioral information not present in annotations. It also implies the file must be a publicly reachable URL. This adds significant value beyond the structured 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?

The description is two sentences long, each adding crucial information. The first sentence states the core action and configurable aspects (image types, DPI). The second sentence explains the async pattern and result retrieval. No extraneous words; every sentence 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 the tool's complexity (6 params, async, no output schema), the description is well-rounded. It explains the input requirements (public URL for file), the async behavior, and the two methods to retrieve results. It does not detail error cases or job status response format, but the presence of a dedicated check-job-status tool mitigates this gap. The description is complete enough for correct invocation.

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 by guidelines the baseline is 3. The description does not repeat parameter details but instead focuses on overall behavior. The schema already adequately explains each parameter (e.g., dpi range, image_type enum, pages expression, webhook_url usage), so no additional parameter information is needed from the description.

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 function: converting PDF pages to images (PNG/JPG/...) at a given DPI. It uses a specific verb ('Render') and resource ('PDF pages as images'), immediately distinguishing it from sibling tools like compress-pdf-file or read-pdf-content. The async behavior and job ID return are also explicitly mentioned.

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 provides explicit guidance on how to handle the async result: either poll check-job-status or provide a webhook_url. This tells the agent exactly how to use the tool correctly. While it doesn't explicitly compare to sibling tools, the purpose is distinct enough that usage context is clear.

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