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

Annotations already mark read-only, and the description adds that the payload includes an untagged count, revealing an extra behavioral detail. No contradictions; it doesn't disclose performance or pagination but is sufficiently transparent for a read-only list.

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 sentence that front-loads the key phrase 'full token registry' and then enumerates the returned fields compactly. No unnecessary words.

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?

For a parameterless list tool with no output schema, the description fully communicates what data is returned and even includes the untagged count. It is complete enough for an agent to invoke correctly.

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?

The tool has no parameters, and schema coverage is complete (empty schema). Per rubric, baseline is 3 since no parameter info is needed in the description.

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 returns the full token registry, listing address, symbol, decimals, and curated tag for every indexed Wanchain token. It distinguishes from get_token (single token lookup) and list_verified_contracts (contracts, not tokens).

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 implies usage for retrieving all tokens but does not explicitly compare with alternatives like get_token or mention when to prefer this over other listing tools. It lacks explicit guidance on when to use this vs. siblings.

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