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

With no annotations, the description carries the full transparency burden and largely succeeds: it discloses auth/payment requirements, the per-chain/hour cadence, attestation/provability details, and the meaning of an empty result via checkedThrough. These are behavioral traits beyond what the schema provides.

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?

Every sentence adds necessary information, but the paragraph is dense and starts with payment details rather than the tool's core purpose. It is not front-loaded or easily scannable; a brief summary line and separation of behavior from parameters would improve it.

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 required parameters and an output schema, the description is essentially complete: it covers auth/cost, alert semantics, filtering options, freshness, attestation, and empty-result interpretation. An agent has enough context to call it correctly.

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 0%, but the description defines the read enum values (vol_spike_long, capitulation_long, onchain_spike_long) and provides defaults and maximums for hours and limit. It also indicates that chain, read, hours, and limit are optional, adding meaning the bare schema lacks.

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 identifies the resource as lead alerts on nine chains, newest first, and enumerates the three alert types with definitions. It lacks an explicit verb like 'list' and does not contrast itself with sibling tools such as latest_signals, so it is clear but not fully differentiated.

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?

It specifies supported chains, alert types, and optional filters with defaults and maximums, which gives an agent enough context to shape a request. It does not explicitly state when to use this tool versus alternatives like verify_lead_alert, so the usage guidance is implied rather than direct.

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