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

No annotations are supplied, so the description carries the entire behavioral burden and delivers none of it. It does not disclose the output form (image URL vs. rendered card vs. HTML), size, caching, region-dependent behavior, or auth requirements — all unknown for a tool whose name implies an image-generation side effect.

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?

It is only two words, but this is under-specification rather than conciseness. There is no front-loaded explanation of purpose, so brevity here is a deficit, not a virtue.

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 no annotations and no output schema, the description should at minimum explain what an 'OG card' response looks like and how it differs from the many sibling og_* and tanks_by_slug tools. It explains nothing, leaving the agent unable to predict the return value or safely call it.

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 100%: slug is documented with an example ('is-7') and region is an enum with a description, so the schema does all the work. The description adds no extra meaning about either parameter, which is the baseline-3 case.

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 phrase 'Tank OG card' names a resource (tank) and an output artifact (OG card) but supplies no verb, so it never says whether the tool fetches, renders, or returns an image. It is close to a restatement of the tool name og_tanks_by_slug rather than a statement of what the tool does.

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?

Nothing indicates when to use this over tanks_by_slug, og_maps_by_slug, or og_tanks_compare. There is no mention of alternatives, prerequisites, or the conditions under which an OG card rather than raw tank data is wanted.

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