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

Annotations already declare a non-read-only, open-world, non-destructive operation, so the bar is lower. The description adds genuinely non-structured context: a 10-credit cost and the fact that execution is asynchronous returning a project id, both of which materially affect how an agent invokes it.

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, each carrying a distinct fact (what it does, cost, async return/next step). Front-loaded with the purpose and no filler.

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?

An output schema exists so return-value detail is unnecessary, and the description covers cost plus the async handoff. It is somewhat thin on the nested style options and the optional `name`, but an agent has enough to call it 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 description coverage is 50% on a nested object; the description only restates that topic and template drive the result and never mentions the optional `name` or `searchWeb` fields. Enum (template = "Random") is already in the schema, so no credit there. Adequate but not compensating for the coverage gap.

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 ("Creates a meme") plus the two inputs that shape the output (topic, template). It is clearly distinct from generic siblings like generate_image or create_gif_or_short_video by virtue of the meme/template framing, though it never explicitly names an alternative.

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 concrete routing information for the follow-up step: the tool starts a background job and returns a project id to hand to wait_for_image_project. It doesn't state when *not* to use this versus generate_image or other image tools, but the async workflow guidance is clear.

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