refresh_preview

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

Only openWorldHint is annotated, so the description carries most of the burden, and it does disclose real side effects: cache-buster mutation, a Facebook re-scrape, and the returned LinkedIn/X artifacts. It omits auth requirements and any platform rate-limit or failure caveats, which matter for a tool that hits Facebook's scraper.

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?

A single dense sentence with the action front-loaded and consequences in a colon-delimited list, so nothing is wasted. It is slightly run-on, bundling the action, side effects, and return values into one clause chain.

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, the description usefully previews what comes back (LinkedIn Post Inspector link, X cache note), which an agent otherwise could not infer. What remains missing is auth/permission context for the external platforms, a real gap for an open-world tool.

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?

One parameter with 0% schema description coverage, so the description must compensate. It implies the input is the page URL whose preview is being refreshed ('a page's link preview'), which gives useful context, but adds nothing about format expectations beyond what the schema's uri format already enforces.

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?

States a specific verb and resource ('Force social platforms to re-fetch a page's link preview') and enumerates the concrete effects (cache-buster bump, Facebook re-scrape). It is clearly distinguishable from siblings like generate_og_image, which produces an image rather than invalidating a cached preview.

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?

Gives an explicit trigger condition: 'after you changed its OG tags or image.' That is clear when-to-use guidance. It stops short of naming a when-not condition or an alternative tool, so it falls short of a 5.

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