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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so the safety profile is covered. The description adds genuinely useful non-schema behavior: a metered cost of $0.01 and the inclusion of derived outputs (verdict, scores, data coverage) that signal the response is a synthesized report rather than raw fields. It does not discuss rate limits or response size for what is clearly a large payload.

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?

One front-loaded sentence with the resource and the 'in one call' framing first, then the payload list, then the price. The field enumeration is long but each item carries selection value; nothing is redundant.

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 correctly discharges the burden of telling the agent what comes back, listing all major sections plus a verdict and data-coverage signal. Combined with fully documented parameters and safe-read annotations, only minor gaps remain (payload size, latency, failure modes).

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 explains base58/0x/coin-type formats and the chain auto-detect default, so a baseline of 3 applies. The description reinforces 'on any chain' but adds no format or disambiguation detail beyond the schema.

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 names a concrete resource (a full token snapshot across any chain) and enumerates the exact payload: price, liquidity, holders, pairs, socials, security flags, scores, verdict, price-impact, coverage. The phrase 'in one call' implicitly separates it from narrow siblings like check_token_price or check_token_security, though it never names them outright.

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 reader can infer this is the aggregate route when multiple data facets are needed, and the explicit $0.01 cost helps with cost/benefit decisions versus cheaper single-purpose siblings. However, there is no explicit when-to-use or when-not-to-use statement and no sibling is named as an alternative, so routing is left to inference.

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