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

Annotations already disclose openWorldHint=true (URL capture), idempotentHint=true and destructiveHint=false, and the description adds three non-obvious behaviors the annotations do not carry: monthly quota consumption per successful call, nothing is persisted, and the image is returned inline. That is real added value, though error/failure behavior (e.g. no source supplied) is left unstated.

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, no filler, with the source-selection constraint front-loaded and cost/persistence notes compressed into a single trailing clause. Every clause 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?

For a 0-required-parameter, nested-object tool with no output schema, the description covers the essentials: how the image comes back (inline) and the one-source rule that prevents an invalid empty call. It omits failure modes and quota-exhaustion behavior, a minor gap given the rich schema.

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 88%, so the schema carries the per-parameter burden and a baseline 3 applies. The description still adds semantics beyond the schema by expressing mutual exclusivity ('exactly one source') and the pairing relationships (template/template_id each filled with data), which the flat schema does not convey.

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 (PNG image) plus concrete output exemplars (social card, certificate, chart). It names the exact set of accepted sources, which immediately separates it from render_pdf and the template CRUD 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?

The 'from exactly one source' constraint and the enumerated alternatives (html, markdown, url, template+data, template_id+data) tell the agent precisely which input path to pick. It stops short of explicitly routing the agent to render_pdf for PDF output or naming when-not-to-use conditions, so it is clear context without exclusions.

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