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

Annotations already mark this as read-only and open-world, and the description adds substantial context beyond them: it states limitations (not policy certification or guaranteed detection), data-handling constraints (no target payment or request bodies stored), public-HTTPS-only scope, trial/payment behavior, and what happens if payment is required. These details materially improve safe invocation.

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 purpose is front-loaded, but the description is heavily bloated with repeated disclaimers, duplicate price statements, illustrative-output caveats, and lengthy payment instructions. Much of this is useful operationally, but the repetition and volume reduce clarity and make it harder to extract the core tool-selection and invocation guidance.

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 names returned fields and includes an illustrative output excerpt, and it covers key safety and payment constraints. It is complete enough to understand the tool's scope and billing model, though the lack of method semantics and sibling-routing guidance leaves minor gaps.

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?

Schema description coverage is 0%, so the description needs to compensate for two required parameters. It adds only the useful constraint that the URL must be public HTTPS and repeats a minimal example; it does not explain the method enum values GET/HEAD/POST, when each is appropriate, or why method matters for the screen.

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 states a specific verb and resource: CDP technical validation plus a bounded heuristic metadata screen for Bazaar listings. It also enumerates what is screened (agent-directed instructions, embedded URLs, tool calls, invisible Unicode, long fields, anomalous prices) and what is returned. It is clear, but it does not explicitly distinguish itself from close siblings such as check_listing or check_endpoint.

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 explains the screening behavior and heavily covers payment mechanics, but it gives no explicit when-to-use guidance versus alternatives. With siblings like check_listing, check_endpoint, and lint_endpoint present, an agent must infer selection rather than being routed by the description.

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