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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuine domain context by naming the specific aggregates it returns (fee mode variants, safety grade components like snipers, bundles, dev activity, creator lock), which is behavior beyond the annotations. It still omits how the grade is computed, whether any field can be null for ungraduated coins, and the cost/latency of a multi-source aggregation.

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?

A single front-loaded sentence with the scope stated first and the field inventory following as a compact list. No filler or hedging. The enumeration is long, but each item tells the agent about data availability, so it largely earns its length.

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?

There is no output schema, so the description must carry the return-value burden, and it makes a reasonable attempt by listing the payload contents. It falls short on structure — the agent cannot tell whether the response is flat, nested, what units prices are in, or how 'graduation progress' and the safety grade are represented. Adequate for a read-only aggregate but not fully 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?

With one parameter at 100% schema coverage, the schema already documents the mint address, its base58 pattern, and even the 'ends in high' hint. The description adds nothing about the mint parameter, so the baseline of 3 applies — the schema is doing the entire job here.

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+resource framing ('Everything about one coin') and enumerates the payload: price, market cap, graduation progress, fee mode, holder concentration, and safety grade. An agent immediately knows this is an aggregate single-coin snapshot rather than a time series or trade list. It does not, however, explicitly distinguish itself from overlapping siblings like get_coin_holders or rug_check, which surface some of the same data.

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 when-to-use or when-not-to-use guidance. The phrase 'Everything about one coin' weakly implies a one-shot overview use case, but the tool shares territory with get_coin_holders (holder concentration), get_coin_fees (fee mode), and rug_check (safety grade), and nothing tells the agent which to pick or whether this supersedes them.

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