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

Annotations declare readOnlyHint=true and openWorldHint=false, so the safety profile is already covered by structured data. The description adds only the output format (1200x630 PNG), which is genuinely useful given there is no output schema, but says nothing about determinism, caching, hosting/URL return, or whether repeated calls reuse the same asset.

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?

A single dense sentence with the output artifact and its dimensions front-loaded and zero filler. 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 6-parameter generator with no output schema, the description usefully pins down the produced image but leaves half the styling parameters unexplained and never states whether a URL, file path, or binary is returned. Adequate but with clear gaps.

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 only 33% across 6 parameters, so the description carries a compensation burden it does not meet. It references 'template and text', loosely covering only template and title; site, theme, accent, and subtitle are left to the schema's bare enum/type declarations.

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?

Names a specific verb (generate) and a precisely specified resource: a 1200x630 PNG social card (og:image). The output format and dimensions make the artifact unambiguous, though it never distinguishes itself from render_pdf or take_screenshot, which are adjacent image-producing 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?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives such as render_pdf or take_screenshot. The agent must infer from the name and the og:image reference that this is for social preview cards.

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