open_graph_preview

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

With no annotations provided, the description must fully disclose behavioral traits. It mentions 'fetches a URL' but omits details like whether it follows redirects, timeout behavior, error handling for invalid URLs, or any rate limiting. This lack of transparency could lead to misuse expectations.

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?

The description is a single, clear sentence with an emoji icon. It is front-loaded with the key verb and resource, and every word contributes meaning. No unnecessary information is present.

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 tool with one parameter and no output schema, the description is adequate but could be more complete by mentioning common use cases, limitations (e.g., only HTTP/HTTPS), or expected output format. The current description meets minimal requirements but leaves gaps.

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 input schema has 100% coverage on the 'url' parameter description, which already explains its purpose. The tool description adds context about extracting OG and Twitter Card tags but does not significantly enhance understanding of the parameter beyond what the schema provides.

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 clearly specifies the action (fetches a URL), the resource (URL), and the extracted data (Open Graph and Twitter Card meta tags) for social sharing preview. It distinguishes itself from sibling tools like 'website_status_checker' by focusing on meta tag extraction rather than status checking.

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?

The description implies usage for social sharing preview but does not explicitly state when to use this tool versus alternatives (e.g., 'website_status_checker' for status checks). No exclusions or prerequisites are mentioned.

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