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

Annotations already declare non-read-only, open-world, and non-idempotent behavior. The description adds that template selection occurs and multiple variants are returned, which is useful but does not disclose fallback behavior (e.g., allowHeuristicFallback) or external service dependencies. No contradiction with annotations.

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?

The description is a single, front-loaded sentence with no redundant words. It efficiently conveys the core function without fluff.

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 tool with 8 parameters, no output schema, and moderate complexity, the description is terse. It does not explain the return format or how template selection works, but the schema fills in parameter details. The description is adequate but not comprehensive for an agent to fully anticipate tool behavior.

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 100% with detailed descriptions for all 8 parameters, so the description need not repeat parameter meanings. Baseline 3 is appropriate as the description adds no parameter-level detail beyond what the schema already provides.

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?

The description states a clear action: 'Select an existing meme template, generate captions, and return one or more meme variants.' This is a specific verb+resource description that distinguishes it from siblings like generate_gif (which makes GIFs) and caption_template (which may only caption).

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 description implies usage for creating meme variants from templates but does not explicitly compare with sibling tools such as caption_template, search_templates, or get_template_ideas. There is no when-to-use guidance or exclusion, so it relies on the agent to infer the appropriate context.

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