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

With no annotations, the description carries the full burden. It usefully discloses the output format (SVG) and that the operation is free, but says nothing about image dimensions, generation latency, how named themes resolve, or any rate limits/auth needs.

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?

A single tight sentence with the purpose front-loaded. 'Free' and '(SVG)' are minor trailing extras but still load-bearing enough not to be waste.

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 simple three-param generator with no output schema, the description plus schema is minimally sufficient, but with no annotations and no enumeration of theme values it leaves the agent guessing about valid inputs and result characteristics.

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?

The description enumerates title, subtitle, and theme and marks the latter two optional, which is about all the schema at 67% coverage already conveys. It adds no syntax, format, or valid-value information (e.g. what theme names are accepted), so it does not compensate for the uncovered subtitle parameter.

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 (Generate) and resource (social/OpenGraph preview image) plus the concrete output format (SVG). The word 'OpenGraph' naturally separates it from siblings like generate_chart and generate_qr, though the description never explicitly names or contrasts those alternatives.

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 explicit when-to-use or when-not-to-use guidance and no named alternative, even though generate_chart and generate_qr are close siblings that an agent could confuse with this. 'Free' hints at a cost distinction (relevant given list_premium_tools) but is not framed as a selection criterion.

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