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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint), so the description's added value is the result semantics: a look-alike answer names the imitated token, and another issuer's listed token is reported as unknown with an issuer_list field. That is real behavioral content, but with no output schema there is no fuller picture of the response shape or what an "unknown" verdict should imply for the caller.

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 purpose and pre-purchase trigger are front-loaded in the first clause, and the short "Free." sentence earns its place as a decision-relevant fact. The closing sentence referencing the equivalent REST endpoint is slightly extraneous for a tool-calling agent but is compact and supports consistency checks.

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 a single required parameter, no nested objects, and no output schema, the description carries most of the burden for return semantics and does deliver the three verdict categories plus one named field. It remains thin on the full response shape for verified/look-alike results, which is the main residual 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 coverage is 100% and the schema already specifies the 0x + 40 hex format, so the description does not need to repeat it. It does add meaning the schema lacks: the address is interpreted on Robinhood Chain, which matters because an EVM address is otherwise chain-agnostic and could produce a different verdict elsewhere.

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 opens with a specific verb and resource ("Check a contract address on Robinhood Chain") and enumerates the three outcome classes the tool resolves an address into: Robinhood-listed, known look-alike, or unknown. That makes the operation clearly a verdict/classification tool rather than a lookup like find_token or token_snapshot, though it never names those siblings to draw the line explicitly.

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?

It gives concrete trigger context: "before buying, holding or accepting it," which tells the agent exactly which workflow step calls for this tool, and "Free" removes a cost consideration. It stops short of naming an alternative tool or a when-not-to-use condition.

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