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

Annotations already declare the operation read-only and non-destructive. The description adds the scope ('source-verified Wanchain contracts') and the fact that it returns a roster rather than a single contract, but it does not disclose pagination, ordering, result shape, or any rate-limit concerns. This is modest value beyond the annotations.

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 one short, direct sentence with no filler or repetition. It is front-loaded with the key resource information, although it sacrifices helpful detail for brevity.

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 is simple and annotated as read-only, but there is no output schema and the description does not explain what fields each verified contract entry contains, how limit affects the response, or whether pagination exists. This is enough to make a default call, but not enough to confidently handle different result sizes or interpret the output.

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 sole parameter, limit, is not explained in the description and the schema provides only its type and default value. With 0% schema description coverage, the description was responsible for explaining limit semantics, but it never mentions pagination, maximum values, or how the limit affects results. The name and default give a weak hint, but the gap remains.

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 identifies a specific resource—source-verified Wanchain contracts—and the word 'roster' implies a listing operation. It is distinguishable from the sibling get_verified_contract, which is singular, but the description does not explicitly state 'list' as the action or name that alternative.

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 guidance about when to use this tool versus get_verified_contract, list_tokens, or other siblings. No alternatives, exclusions, or conditions are mentioned, so an agent must infer usage solely from the tool name.

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