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

With no annotations, the description carries the full burden, and it does disclose the single most non-obvious trait: no PNG is returned, only card data, and the caller must render the image at report_url. It says nothing about failure behavior when a URL is unreachable, whether title/description override scraped values, or any rate/network constraints, so significant behavioral ground is left uncovered.

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 tight sentences, zero filler, with the capability stated first and the critical render-at-report_url caveat immediately after. Every clause contributes information an agent needs before calling.

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 three-parameter tool with no annotations and no output schema, the definition is only roughly adequate: it hints that 'card data' comes back but never enumerates or characterizes it, and report_url is referenced without explanation. Combined with the undocumented override behavior, an agent could call it correctly but could not reliably predict the response.

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 33% – only url is documented, while title and description have no schema text. The phrase 'from a URL or from text' usefully suggests these are an alternative input path rather than required companions, which is real added meaning. It still omits the precedence rule when both URL and text are supplied, which is the ambiguity an agent is most likely to hit.

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 names a specific action and artifact: resolving title/description/favicon and producing a 1200x630 Open Graph card, with two input modes (URL or text). That is far more specific than the title alone and clearly separates it from siblings like preview_meta. It stops short of a 5 because 'generate' is qualified only by the follow-on sentence, so the deliverable read at first glance could suggest a returned image.

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?

It implies when to use the tool through the input modes ('from a URL or from text') but never states conditions, prerequisites, or when a sibling such as preview_meta would be the better choice. An agent must infer the routing decision rather than read it.

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