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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds real behavioral context beyond them: no API key required, every number carries source and time, implausible numbers are withheld rather than guessed, and no orders/funds are touched. These are useful disclosures for a data-reference tool.

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 enumeration is front-loaded and useful, but the tail is padded with promotional and legal boilerplate ('Places no orders, moves no funds', 'Not financial advice') that doesn't help an agent select or invoke the tool. It reads as one dense paragraph rather than a tight, purpose-built definition.

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 zero-parameter reference tool with no output schema, the description covers what the tool returns (the alert kinds, their check cadence, and delivery) thoroughly enough to call it correctly. Missing only explicit routing guidance relative to the sibling alert tools.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. No parameter details are needed or missing.

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 resource: the categories of alerts the system can send about a coin, enumerating them (price above/below, 24h/7d change, market cap, volume, Animal Spirits, buzz). An agent can tell this is a reference/enumeration tool, distinct from crypto_alert_create or crypto_alerts_list. It stops short of explicitly contrasting with those siblings by name.

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?

There is no explicit when-to-use guidance — nothing says to consult this before calling crypto_alert_create to learn valid alert kinds, nor any exclusion. Usage is only implied by the enumeration of alert types.

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