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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description still adds real value beyond them: it names the data provenance ('third-party on-chain analysis'), explains the scale direction of the risk score ('0 is lowest risk') which prevents inversion errors, and lists each signal returned. It omits what happens for unknown or non-token mints and any rate/coverage caveats.

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?

Front-loaded with the action and input, then a single dense clause enumerating outputs, closing with a short disclaimer. The output enumeration is long but each item is informative; only the disclaimer sentence is arguably padding.

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 takes on the burden of describing return values and does so thoroughly, including score range direction and warning list. It is nearly complete for a read-only lookup, but leaves error/empty-result behavior and the meaning of 'risk level' buckets unstated.

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 description coverage is 100% with a single well-documented 'mint' parameter (base58, 32-44 chars), so the schema carries parameter meaning. The description only restates 'by mint address' and adds no format or validation detail beyond it, which matches the baseline for fully covered schemas.

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?

States a specific verb and resource ('Looks up a Solana token by mint address') and enumerates the returned safety report contents in detail. It does not, however, distinguish itself from siblings like get_token_holders, even though the description already claims to report 'top-holder concentration', which overlaps with that tool.

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?

Usage is implied by the framing 'safety report' and the clause 'Read-only and informational; not financial advice', which tells the agent the output is advisory, not an action trigger. There is no explicit statement of when to prefer this over get_token_holders or explain_risk_signals, and no prerequisites or exclusion cases are given.

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