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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral nuance beyond annotations: meta.verdict is the lead output, the rest is supporting evidence, and a clean read is not a buy signal. This is useful interpretive context for an agent.

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 compact, front-loaded with the core purpose, and every sentence earns its place. The list of returned fields is efficient, and the caveat about clean reads is essential context rather than filler.

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?

Given there is no output schema, the description does enough by naming the major output sections and explaining how to interpret meta.verdict. It could be more explicit about error cases or the exact return shape, but for invoking the tool correctly with one parameter, it is sufficiently 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?

Schema description coverage is 0%, so the description must compensate. It does by specifying that the single parameter 'mint' is a base58 Solana mint address. This adds real meaning beyond the bare schema and is adequate for a one-parameter tool.

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 identifies the resource (Solana token by mint) and enumerates the data returned: holders, bundled-launch read, deployer holdings, socials, and meta.verdict. It reads as a specific lookup tool, though it does not explicitly differentiate itself from siblings like rh_token_safety.

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 any Solana token lookup and gives a reading order ('Start from meta.verdict'). However, it never states when to choose this tool over sibling tools, nor does it mention exclusions or alternatives.

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