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

With no annotations, the description carries the full burden and does well: it discloses the return contract (SAFE/CAUTION/DANGER with reasons), the rate limit (5 free checks/day), and the paid fallback. It stops short of stating that the live sell-route test makes real network calls (latency/timeout behavior) or whether any auth/API key is needed for the free tier.

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?

Three dense sentences, front-loaded with purpose, then checks, then verdict format and quota. Every clause conveys distinct information with no 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?

For a single-parameter tool with no output schema or annotations, the description covers the verdict format, the checks performed, and the quota/pricing model, which is what an agent needs to call and interpret it. Minor gaps remain around latency from the live sell-route test and any auth requirements.

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?

Only one parameter and schema description coverage is 100%, so the schema already documents 'mint' as a Solana token mint address. The description adds no format, network, or validation detail beyond what the schema provides, so the baseline of 3 applies.

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+resource ('Rug/safety check for a Solana token') and enumerates exactly what is inspected: mint & freeze authority, Token-2022 settings, real-wallet holder concentration, live sell-route test. An agent can distinguish this from mosn_safe_swap (swapping) and mosn_paid_endpoints (payment/endpoint listing) without opening any schema.

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?

Gives a concrete usage constraint and routing rule: '5 free checks per day, then use the paid x402 endpoint,' which names an alternative path. It does not, however, state when this check should be run versus the sibling tools (e.g., before a swap via mosn_safe_swap), leaving the sibling-selection decision implicit.

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