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

Annotations only mark this as non-read-only, non-destructive and non-idempotent; the description adds the substantive traits — it is always asynchronous, returns a token rather than a file, the download URL is temporary, and there is a concurrency limit. That is real context an agent cannot get from the structured fields.

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?

Opens with the operation class ('WRITE (render job)'), then the action, then the required follow-up workflow, then the constraint. Every sentence carries distinct information with no repetition of the schema.

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?

There is no output schema, and the description compensates fully by describing what comes back (status plus a token) and how to turn that into the user-visible result (poll, then present the temporary URL). The concurrency limit rounds out what an agent needs to invoke this 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 coverage is 100% and the descriptions for zoom (PNG only) and page_size (PDF only) already explain format-specific applicability, so the schema does the heavy lifting. The description adds marginal value by binding 'PDF or PNG' to the format parameter and exposing the underlying async=true endpoint convention, but adds nothing on recipe_id or the ranges.

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?

States a specific verb and resource ('start rendering a recipe's nutrition label as a PDF or PNG') plus the return shape ('render status with a token'). This clearly separates it from recipal_get_label (retrieval) and recipal_get_label_render_status (polling) among the siblings.

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?

Gives an explicit workflow: call this, then always poll recipal_get_label_render_status with the token, then hand the user the temporary download URL. It also names the parallel-render cap (5 per account), so the agent knows the operational constraint before calling.

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