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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: no indication of whether this renders an image, returns markup, or what content-types/format the caller gets back. For a tool with zero structured behavioral coverage this is a complete gap.

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 words is brevity by under-specification rather than by editing; the sentence is front-loaded but omits the information an agent needs. It is not a wasteful sentence so much as an insufficient one.

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?

There is no output schema and no annotations, so the description is the only source of information about this tool, and it says nothing about behavior or return values. An agent cannot determine what calling it produces.

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% and both parameters (title, subtitle) are self-documenting, so the baseline is 3. The description adds no extra meaning such as whether these are required, default text, or escape/formatting rules, so it does not rise above baseline.

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?

"Generic OG card" restates the tool name (og) plus a category label and never states an action or resource. It does not explain that this likely renders an Open Graph image/card, nor how it differs from the many og_* siblings like og_clans_by_tag or og_maps_by_slug.

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?

There is no statement of when to use this generic card versus the entity-specific og_* variants. The word "Generic" hints at a fallback role, but the agent must infer that; no condition or alternative is named.

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