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

The annotations already indicate readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description adds useful behavioral context beyond these: the per-call cost ('$0.01/call, x402 (USDC on base)') and the multi-platform scope (Telegram, WhatsApp, X, LinkedIn, Slack, Facebook & Discord). It also mentions validation and issue detection, but does not disclose return format or rate limits.

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 two sentences, front-loaded with the core purpose and then expanding into details and pricing. Every sentence adds value—there is no fluff or redundancy. The pricing note is tacked on but informative.

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 has no output schema, so the description should explain what the tool returns. It does mention 'find what breaks your link previews' which gives partial insight, but it does not describe the output structure (e.g., per-URL previews, audit report). The annotations and schema are simple, so some additional return-value context would improve completeness.

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 fully describes both parameters (urls and maxConcurrency) with descriptions, so the baseline is 3. The description does not add extra meaning to these parameters beyond what the schema provides. 'Bulk-audit' loosely implies batching but does not enhance parameter semantics.

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 states the tool's function with specific verbs: 'See exactly how your links look...', 'Bulk-audit Open Graph and Twitter Card tags', 'validate preview images', and 'find what breaks your link previews'. It names the specific resources (links, OG tags, preview images) and distinguishes from siblings like ai-crawler-access-checker.

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 when you want to check social media link previews or audit meta tags, but it does not explicitly say when to use this tool vs alternatives. There are no exclusions or alternative tool names mentioned. The intended context is clear but not explicitly articulated.

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