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

With no annotations, the description must carry the transparency burden. It discloses the deterministic HEAD/GET method, the PASS/FAIL output, and the $0.01 USDC per-call cost. However, it does not mention auth requirements, error handling, rate limits beyond cost, or whether it follows redirects.

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 core behavior is front-loaded in one dense sentence, followed by a business context code and cost. The SKU identifier is noise for an AI agent, but it is brief and does not undermine clarity. No superfluous filler.

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 tool with no annotations, no output schema, and only a single vague parameter, the description omits critical details: what constitutes a valid task, output formatting, failure behavior, and whether the parameter is truly optional. The agent is left to guess how to construct input and interpret the verdict response.

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 schema only says the 'task' is 'Task/query text for this SKU', which is vague. The description adds that the task contains URLs, but does not specify their format (e.g., newline-separated, list, URL array) or whether an empty task is allowed, leaving ambiguity for a single required-ish parameter.

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 names a specific verb ('check'), a specific resource ('every URL in the task'), and a specific output ('PASS/FAIL verdict with per-URL status codes'). It is distinct from sibling tools like data.web-extract or ops.due-diligence-scan, which do not cover link integrity 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 phrase 'Post-deploy verification SKU' provides an implicit usage context, but no alternatives, exclusions, or concrete when-to-use guidance are given. An agent is not told why to select this over other verification or scanning tools.

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