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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals the exact data sources (GoPlus, Blockscout, DEX), specific checks performed (honeypot, tax, blacklist, pausable, mintable, holder concentration, liquidity), and an output trait ('Every flag names its source'). This is a thorough and honest account of behavior, superior to most tool descriptions.

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 dense but well-structured, leading with the main purpose and then detailing sources and checks. Every sentence provides useful information, though it is somewhat long. It avoids fluff while packing essential details, deserving a 4.

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?

The tool has no output schema, so the description must hint at return values. It mentions 'Every flag names its source' and lists the verdict types (honeypot, rug, safe to buy). For a moderately complex tool with three data sources, this provides enough context for an agent to understand what it will receive, though a formal output structure is not described. The completeness is good but not perfect.

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 baseline is 3. The description adds marginal value by emphasizing the address is on Robinhood Chain and that the scan is by 0x address, but it does not add syntax or format details beyond the schema. The schema already documents both parameters adequately.

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 the tool performs a 'Full safety scan' for a Robinhood-chain token by address, listing specific checks from three sources. It distinguishes itself from sibling tool token_security by claiming to be more complete for Robinhood tokens. This meets the criteria of a specific verb+resource+scope with sibling differentiation.

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 positions this as 'THE tool for is this Robinhood coin a honeypot / rug / safe to buy' and states it is 'More complete than token_security alone for Robinhood tokens.' This gives clear context on when to use it, but it does not explicitly mention when not to use it or name alternatives beyond token_security. Thus it earns a 4 for clear context without exclusions.

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