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

The description explicitly discloses that the operation is asynchronous and returns a polling structure: '{ jobId, status, poll }'. This goes beyond the annotations by explaining the non-immediate nature of the job and how the caller should track it. It does not contradict the readOnlyHint.

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 a single efficient sentence that front-loads the core action and input modes, followed by a compact output shape. Every element provides useful information with no redundancy or filler.

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 essential input modes and async output shape, but it does not explain how the poll result leads to the final PDF, what status values mean, or how to handle failure. Given the lack of an output schema, more detail about the polling workflow would make the tool safer and easier to use.

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?

With 0% schema description coverage, the description partially compensates by stating 'from a URL or HTML', which maps to the url and html parameters and clarifies that exactly one should be supplied. However, it does not mention the format parameter or its A4/Letter enum, leaving that aspect solely to the schema.

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 a specific action and resource: 'Render a PDF from a URL or HTML'. It also notes this is an async job, which further clarifies the nature of the operation. This clearly differentiates it from sibling tools like screenshot capture or image generation.

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 implies the primary use case: provide a URL or HTML to render a PDF. However, it does not explicitly explain when to choose this tool over alternatives like forgekit_capture_screenshot or forgekit_generate_og_image, nor does it state any exclusions or prerequisites.

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