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

Annotations already declare readOnly, non-destructive and open-world, so the safety profile is covered; the description adds what annotations cannot: an API key is required, fresh reads are metered (3/day free then 1 credit), and cached reads are free. It does not disclose failure behavior for an invalid or unknown mint, nor latency, which is the main remaining gap.

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 pairs the operation with its return fields, followed by a short cost/auth sentence; nothing is padding. The 'bagcheck.lite.v1' version tag and 'Not financial advice' boilerplate are mildly wasteful but defensible as provenance and disclaimer.

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 carries the return-field inventory, plus auth and billing constraints an agent needs before calling. What is missing is minor for a lite read: error/edge behavior for a bad or unknown mint, and whether a fresh read is forced when max_data_age_seconds=0.

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%, so baseline is 3; the description earns the extra point by explaining that cached reads are free, which is the practical reason an agent would raise max_data_age_seconds toward its 600s default or 3600s ceiling. It does not restate the base58 mint format, but the schema handles that fully.

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 ('Lite read' of a Solana token) and enumerates exactly what the payload contains: verdict, top-10 holder %, dev stake, launch buy / dev sold, KOL wallets holding, basic flags. It does not explicitly distinguish itself from sibling check_solana_token_basic or analyze_solana_token, so the agent must infer that 'lite' means a shallower, cheaper tier.

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 'Lite' label and the credit pricing imply this is the cheap first-pass screening call, but there is no explicit when-to-use or when-to-escalate guidance relative to check_solana_token_basic or analyze_solana_token. The quota sentence ('Free for 3 fresh reads per day, then 1 credit') hints at a cost-tier decision but never states the alternative.

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