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

Annotations already mark the tool as read-only and open-world, so the safety profile is covered. The description adds meaningful context by stating that the URL must be public and by enumerating the exact output fields, which is especially valuable given there is no output schema.

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 sentence that states the operation and then provides a compact output contract. Every element is useful and placed before any less relevant detail, with no redundancy.

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?

The tool is simple, has one parameter, and is fully covered by annotations for read-only/open-world behavior. The description provides the output shape, which compensates for the absent output schema, leaving no critical missing information for correct invocation.

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?

With 0% schema description coverage, the description partially compensates by identifying the input as a 'public URL' and implying the url parameter's expected nature. However, it does not add much detail beyond what the input schema's 'url' field and 'format': 'uri' already convey.

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 uses a specific verb ('Fetch') and identifies the exact resource ('Open Graph / Twitter Card metadata from a public URL'). It is unambiguous and clearly distinguishable from sibling tools like forgekit_capture_screenshot or forgekit_generate_og_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?

The description implies the tool is for public URLs that expose social metadata, but it does not explicitly state when to choose this over alternatives or when it should not be used. The context is clear enough for a single-purpose tool, but no exclusions or alternative routing are provided.

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