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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds useful context beyond annotations: local cache refreshed every 30 minutes, dataset size, CC0 licensing, and x402/Solana pricing. It does not describe exact response shape, but the safety profile is already covered.

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 front-loaded with purpose and modes, then layers on dataset, cache, licensing, pricing, and HTTPS endpoint details. It is dense but earns most of its space; the marketplace/payment details are slightly peripheral but relevant for invocation.

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 five optional parameters, no required parameters, 100% schema description coverage, and safety annotations, the description gives enough context to select the correct mode. It does not fully specify the return shape for each mode, but no output schema exists and the key listing fields (date, reason) are mentioned.

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 100%, so the schema already documents all five parameters. The description adds mode-level semantics by grouping sha1 and ip as lookup modes and limit/since/reason as list-mode filters, which helps an agent understand mutually exclusive parameter uses.

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 resource (abuse.ch SSLBL) and three concrete operations: checking a certificate SHA1 fingerprint, checking an IP against the botnet C2 IP list, and listing recent blacklisted certificates. This distinguishes it clearly from sibling tools like ssl_cert_info or generic IP reputation 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?

The description explains which parameters select which mode: sha1 for certificate lookup, ip for IP-list lookup, and reason/since/limit for list mode. It does not explicitly name when to avoid this tool or compare it to alternatives, but the operational context is clear.

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