Full decoy / zombie blacklist

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

Although no annotations are provided, the description fully discloses cost and caching recommendation. It implies a read-only operation with no side effects. Lacks details on rate limits or error responses, but for a simple data retrieval tool, it is sufficiently transparent.

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?

Two sentences, front-loaded with the core purpose, then immediately followed by actionable usage guidance and cost. No wasted words; every sentence earns its place.

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?

Given zero parameters and no output schema, the description covers purpose, cost, and usage pattern. Minor gaps: does not mention authentication requirements or typical result size. Still fairly complete for a simple blacklist 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?

No parameters exist, so baseline is 4. Description adds value by specifying what is returned (active endpoints + counts), going beyond the empty schema.

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?

Description clearly states it returns active flagged x402 endpoints with per-reason counts. Verb 'returns' and specific resource ('catalog of decoys/zombie blacklist') make purpose unambiguous. Distinguishes from siblings by noting it's a blacklist meant for periodic caching, unlike preflight or other tools.

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?

Explicitly advises to pull periodically and cache locally, and contrasts with 'preflighting every URL' as a cheaper alternative. Provides cost context ($0.005 USDC). Could be more explicit about when not to use, but gives clear context on the intended use case.

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