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

No annotations are provided, so the description carries the burden. It discloses a side effect ('records the fresh reading') and its comparative approach, but does not elaborate on persistence, reversibility, or required permissions. This is partial transparency.

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 three sentences and front-loaded with the core question. Some redundancy exists between 'Did this token survive or RUG?' and 'Answers 'did it rug / is it dead / can I still sell'', but overall it is compact and readable.

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 or annotations, the description provides the essential context: what the tool does, when it's most useful, and what questions it answers. However, it does not specify the exact return format or the operational implications of 'recording,' leaving some gaps.

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% for both parameters. The description's instruction 'Give a contract/mint address' reinforces the 'address' parameter but adds no meaningful detail beyond the schema. The chain hint is also not elaborated.

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 states the tool's function with specific verbs ('Re-reads live liquidity/volume and compares...', 'records the fresh reading') and the resource (token outcome). It distinguishes itself from sibling tools like rug_check or token_security by focusing on survival based on historical comparison, making its purpose unambiguous.

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 provides contextual guidance: 'Works on any chain incl. Solana + Robinhood' and 'most powerful on a token fingers has history on.' This implies when the tool is most useful (when historical data exists) but does not explicitly exclude alternatives or name when-not-to-use.

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