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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely non-obvious operational context: it is a paid HTTP endpoint (/v1/sol-mint), requires an X-API-Key header on the MCP POST, and costs 1 credit per successful call with no demo limit for prepaid credits. The referral-earnings paragraph adds nothing an agent needs to invoke the tool and dilutes this.

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 first two sentences are well front-loaded and contain everything needed to select and call the tool. The remainder is promotional bulk: x402 pack pricing, credit mechanics, and a long referral clause with revenue-share percentages, settlement cadence, and a separate endpoint — content that does not help an agent decide to invoke this tool.

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?

An output schema exists, so return values need not be re-explained, and for a one-parameter read-only check the description covers purpose, scope, cost, and auth. It is sufficiently complete to call correctly; the only surplus is referral material that adds no operational completeness.

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?

There is a single required parameter with 100% schema description coverage ('Solana mint address (base58)'), so the schema already carries the semantics. The description mentions mint authorities but does not clarify the input format, whether Token-2022 mints are accepted identically, or how to obtain the address — baseline 3 applies when the schema does the work.

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 ('Rule-based safety check of a Solana SPL / Token-2022 mint') and enumerates exactly what is examined: mint & freeze authority, permanent delegate, transfer hook/fee, pausable, default-frozen, largest-holder concentration. The returned riskScore and verdict are named, and the subject matter is unmistakably distinct from siblings like email_check or web_read_markdown.

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 domain — an agent inspecting a Solana mint knows this is the relevant tool — and the paid-endpoint details suggest the context is programmatic risk screening. But there is no explicit 'use this when X, not Y' guidance, no statement of when a check is unnecessary, and no comparison to the x402_* siblings that also gate payment flows.

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