btc_abuse_check

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real context beyond that: it names the external data source and states the authentication requirement, which the agent must satisfy before calling. It stops short of covering rate limits or empty-result semantics.

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?

Three short sentences, each carrying distinct information: what it does, what it returns, and what it requires. Front-loaded with the purpose and zero 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?

With no output schema, the description helpfully summarizes the return shape (scam reports with categories and descriptions), and annotations carry the safety profile. It is nearly complete for a one-parameter read tool, though it says nothing about behavior when no reports exist or about rate limits.

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% and there is a single required parameter whose meaning ('Bitcoin address to check') is fully documented in the schema. The description adds no format or validation detail beyond that, so the baseline of 3 applies.

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?

States a specific verb (check) and resource (Bitcoin address) plus the data source (ChainAbuse) and what is returned. This clearly differentiates it from the generic btc_address/btc_balance/btc_tx siblings, which cover address data rather than abuse reports.

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 names the prerequisite (CHAINABUSE_API_KEY) but gives no explicit when-to-use or when-not-to-use guidance relative to btc_address or the other abuse-check siblings (abuseipdb_check, threatfoxSearch). Usage is only implied by the purpose statement.

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