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

Annotations only cover the safety profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=false); the description adds the operationally important facts: one-shot behavior, a per-member cap of 10 active alerts, one-minute evaluation cadence, and outbound webhook delivery. The non-idempotent annotation is corroborated by the 'one-shot' semantics rather than contradicted.

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 purpose and cadence are front-loaded, and the dense type-by-type breakdown each earns its place by defining a distinct trigger. It is a long single block, but there is little redundant wording and no marketing 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?

With no output schema, the description still tells the agent where results appear (check_alerts), how delivery works (webhook), the quota, and the one-shot nature. For a 5-parameter mutation tool, an agent has everything needed to invoke 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 coverage is only 60%, and the description compensates heavily on the most consequential parameter, threshold: dollars for price alerts, percent for oi_change/funding_extreme, a signed value (negative for a drop) for oi_change, and no threshold at all for magnet_hit. It also adds a constraint missing from the schema (etf_flip coin must be BTC or ETH), though the 'note' parameter remains undocumented in both places.

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 and resource ('Sets an alert on OwlChart data') plus a behavioral detail ('checked every minute'), and the type enumeration distinguishes it from the sibling read/manage tools check_alerts, list_alerts and delete_alert. An agent can identify the tool's role without opening the 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?

The description gives clear context for when each alert type applies, what fires it, and where the result surfaces ('shows in check_alerts'), which effectively routes an agent to the creation flow versus the inspection flow. It does not, however, state exclusions or prerequisites explicitly (e.g. when to prefer list_alerts or delete_alert, or account requirements).

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