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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered and the bar is lower. The description adds that output is captioned artwork in PNG, which is real behavioral context, but it discloses nothing about caption placement, fallback behavior, or failure modes beyond what the schema states.

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, zero filler, and the core resource plus output format are front-loaded before the input-mode detail. 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?

All six parameters are optional and an output schema exists, so return values need no explanation. The description covers both invocation modes and the PRG output, though it omits the gradient style ids and caption parameters—minor given the schema documents them.

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 67%, so part of the burden falls on the description. It clarifies the accepted image input forms (base64, data URI, public URL) and the image-vs-gradient choice, but says nothing about 'top'/'bottom', 'upper', 'styleId' values, or 'fontScale', leaving several parameters only documented in 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?

Specific verb (Render), specific resource (top/bottom-caption meme), and explicit output format (PNG). No sibling (make_collage, resize_social_image, generate_qr_code) does meme captioning, so an agent can identify this immediately.

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?

States the two input modes—'give it an image ... or pick a gradient style'—which is useful invocation context, and the schema confirms the image parameter is omitted for gradient backgrounds. However, there is no guidance on when to prefer this over sibling image tools, nor any exclusions.

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