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

No annotations are provided, so the description must disclose safety and side effects; it only says it runs the same code the tool page runs. It does not state that it makes an external request, whether it is read-only, how it handles unreachable URLs, or what a 'preview' contains.

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 short and opens with the subject, but the second sentence is vague and the 'Scope: check' fragment is cryptic rather than informative. The structure is three fragments rather than a clear operational summary.

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?

With no output schema and no annotations, the description should explain the preview result and fetch behavior; it does neither. For a one-parameter check tool that is likely to make a live network request and return social metadata, this leaves the agent with insufficient context.

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 single url parameter is fully documented in the schema as needing a full URL including scheme, so the schema carries the parameter semantics. The description adds no URL format, accessibility, or protocol constraints beyond that.

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 only restates the tool name as 'Open Graph and social preview' and never supplies a verb such as fetch, validate, or render. It does not distinguish the tool from nearby checks like check_schema, check_seo_audit, or check_tech_detect.

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 guidance on when to choose this check over sibling checks or when not to use it. The fragment 'Scope: check' does not establish preconditions, exclusions, or alternatives.

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