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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description earns some credit by listing the return payload (template ids, names, slot counts, blank image URLs), which matters since there is no output schema, but it says nothing about result ordering, relevance ranking, or what an empty result looks like.

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, and the core capability is front-loaded ahead of the return-value detail. The parenthetical examples are the most efficient part of the text and directly aid query formulation.

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 two-parameter read-only search with no output schema, the definition covers purpose, query intent, and return shape, which is close to sufficient. The remaining gap is behavioral detail on `limit` and result ordering, which an agent would need to page or size results deliberately.

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 0%, so the schema contributes only min/max constraints and no meaning. The description compensates well for `query` by characterizing it as an emotion, situation, or name with examples, but the `limit` parameter is never mentioned and no default or result-count behavior is given.

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 specific verb and resource ("find meme templates") and qualifies the search dimension as an emotion, situation, or name, with three concrete example queries. It does not explicitly distinguish itself from sibling get_meme_template (lookup by id) or get_trending_meme_templates, so it falls just short of a 5.

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?

Usage is implied rather than stated: an agent can infer this is the keyword-discovery entry point before calling get_meme_template or render_meme, but the description never says so. There are no exclusions or prerequisites, and no mention of when to prefer the trending sibling instead.

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