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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions the check type and data sources, but does not state whether the operation is read-only, what it returns, whether external API calls are made, or any side effects. 'Check' implies non-mutating, but this is not explicit.

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 a single dense sentence that front-loads the key purpose and method. Every word adds relevant context, with no filler or redundant restatement of the tool name.

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 and no annotations, so the description needs to explain what the caller should expect. It does not describe the return format, result granularity, or limitations. For a one-parameter tool this is still a meaningful gap.

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 0%, so the description must compensate. It does partially by clarifying that the address parameter is a Robinhood Chain token address. However, it does not explain expected format, chain details, or whether the address should be a contract address.

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 specific operation: a rug/honeypot/tax/ownership check for a Robinhood Chain token. It also names the method (GoPlus plus LP heuristics), which gives the tool a distinct identity, though it does not explicitly distinguish itself from sibling tools like talon_lp or talon_scan.

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 usage context is implied: an agent can infer this tool is for token safety/rug checks on Robinhood Chain. However, there is no explicit guidance about when to use it versus alternatives, nor any conditions or exclusions.

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