get_og_metadata

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

Describes what data is extracted but does not disclose limitations, error behavior, or performance characteristics. No annotations provided, so description carries burden; it is adequate but not exhaustive.

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?

Concise at three sentences, front-loaded with purpose, then usage, then parameter details. No wasted words.

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 an output schema presumably available, and one simple parameter, description covers purpose, usage, and parameter adequately for an agent to use the tool correctly.

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 explained with a clear example and usage context. Schema provided no parameter description, so description compensates well.

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?

Clearly states extraction of Open Graph metadata, title, description, and favicon from a URL. Distinguishes from sibling tools like 'scrape_meta_tags' by focusing specifically on OG metadata for link previews.

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?

Provides explicit use cases: link previews, content summarization, social media card extraction. Does not mention when not to use or alternatives, but context is clear enough.

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