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

Annotations (readOnlyHint, openWorldHint, idempotentHint) already establish the safety and idempotency profile, so the bar is lower, and the description adds a genuinely non-obvious caveat: `lookalike: null` only means no match against a short list of well-known tokens and is explicitly not a safety verdict. That prevents a real misinterpretation. It stops short of disclosing error behavior for malformed or unknown addresses, so it is not a 5.

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?

Two sentences, no filler; the field inventory and the lookalike warning are both load-bearing given there is no output schema. The weak spot is structural rather than length-related: the first sentence is a verbless fragment, so the subject of the sentence is ambiguous on a first read.

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 properly carries the return-value burden and enumerates the returned fields plus the important lookalike semantics. What is missing is the framing action (what the tool does with chain + address) and failure behavior for unknown or malformed addresses, which is why it falls short of complete.

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 50%: `chain` has an enum description in the schema, but `address` is documented only by a regex pattern with no prose. The description mentions no parameters at all — not the accepted chain values, not the required 0x address format — so it does not compensate for the coverage gap. The 3 baseline applies only when the schema already does the heavy lifting.

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 is a noun phrase listing the fields of a token contract ('name, symbol, decimals, total supply, indexed holder count, and lookalike') rather than stating the action. The resource (a token contract on BNB Chain or Ethereum) is identifiable, and the sibling get_transaction is implicitly distinguished by resource type, but no verb ('returns'/'looks up ... for the given address') is supplied, so the purpose must be inferred from the name and title.

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?

There is no statement of when to call this tool, no prerequisites, and no mention of the sibling get_transaction as an alternative. The only guidance-like content is the caveat about what `lookalike: null` does not mean, which is a behavioral note rather than usage routing.

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