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

With no annotation provided, the description carries the full burden. It lists the on-chain signals it checks and mentions Blockscout as a data source, which gives useful insight. However, it does not explicitly state it is read-only, nor does it mention any potential side effects, rate limits, or error behavior.

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 sentences cover purpose, context, and usage. The description is information-dense without padding, though it could be slightly shorter without losing value.

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 there's no output schema, the description compensates by enumerating the returned signals (VERIFIED status, ERC type, holder count, creator, activity, scam flag). It also provides chain context and an example usage. Missing details like error conditions are minor given the tool's simplicity.

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 coverage is 100%, so the schema already documents both parameters. The description adds only 'Give a 0x collection address' which reinforces the existing schema but doesn't add substantial new meaning. The chain default is already in the 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?

The description clearly states it is a safety check for a ROBINHOOD-CHAIN NFT collection, with a specific verb ('check') and resource. It enumerates the exact signals checked (source VERIFIED, ERC standard, holder count, creator, on-chain activity, scam flag), and distinguishes itself by noting OpenSea's trust signals don't cover Robinhood.

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 explicitly says to use this for legitimacy/rug checks on Robinhood/Anvil NFT collections, and notes it is 'the only read' because OpenSea doesn't cover this chain. It doesn't explicitly mention alternatives for non-Robinhood chains, but the context is clear enough.

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