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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the basic safety profile. The description adds '1.00 USDC' (likely a cost per call) and a 'Not financial advice' disclaimer, which are useful behavioral clues. However, it does not describe output format, error behavior, or any rate limits, so it only partially goes beyond the annotations.

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 very brief (three short sentences) with no wasted words. It front-loads the core purpose and then adds cost and disclaimer. It is not formally structured but is efficient and easy to parse.

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 tool with no output schema, the description should explain what the score represents, its range, or how it should be interpreted. It only says 'score' without details. The cost and disclaimer are useful, but the lack of output semantics makes it incomplete for an agent to know what to do with the result.

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% and the schema already documents 'token' as a token address. The description only repeats 'Requires token' without adding any nuance about address format, examples, or edge cases. Baseline 3 is appropriate since the schema does the heavy lifting.

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 states 'Rule-based memecoin score' which clearly identifies the resource (a score for memecoins) and the method (rule-based). It is not a tautology and provides a specific purpose, though it doesn't elaborate on what the score represents (e.g., risk, quality) or how it differs from sibling tools like token_safety or pair_digest.

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?

No guidance on when to use this tool versus the many siblings. It only states that a token is required and mentions a cost of 1.00 USDC, which is a prerequisite but not a selection criterion. There is no mention of alternatives or conditions that would favor this tool.

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