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

Annotations declare a non-read-only, non-idempotent, closed-world write, and the description adds genuinely useful context beyond them: the work is a durable queued job and consumes one render.image quota per success. That billing and async semantics are exactly the extra behavioral facts annotations cannot express.

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?

Three short sentences, front-loaded with the core action before the async and quota details. Every sentence carries information, though the middle sentence is telegraphic and could be folded in.

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?

For a queued creation tool, the async + quota disclosure plus the existing output schema cover the return path adequately. However, with zero schema description coverage and a nested variables object, an agent still lacks enough to build a correct call, so the definition is only minimally viable.

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 0% across four parameters including a nested 64-property variables object, yet the description says nothing about template_id, format options, variable key/value constraints, or what external_id is for. The single mention of 'variables' is generic and adds no meaning beyond the parameter name.

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 (render) and resource (organisation templates with variables) with a concrete output type (image). It is distinguishable from render.template.get/list and the other render.* producers, though it does not explicitly name or contrast with render.pdf.create or render.screenshot.create.

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?

No statement of when to choose this over render.pdf.create, render.screenshot.create, or render.batch.create, and no prerequisites (template must exist, variables must match the template schema) are given. The only usage signal is implicit: it is queued, so the caller learns it is asynchronous.

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