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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the bar is lower; the description still adds ordering (oldest first, not newest), the pagination contract, and the plan/cost requirement. It does not disclose rate limits or what an empty/expired cursor returns.

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?

Two sentences with the resource and ordering front-loaded, then the paging and auth facts. Every clause carries information; the trailing 'Free.' is terse but still adds cost context.

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 does at least name the alert type and version so the agent knows what comes back, and it covers paging and access requirements. It omits the shape of an alert object and what limit controls, which is a modest remaining gap.

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 50%: cursor is documented inline, limit is not. The description reinforces cursor semantics ('pass next_cursor back to page') but says nothing about limit's default of 50 or its 200 ceiling, leaving the undocumented half unaddressed.

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 ('Alerts ... across your watched coins and wallets'), plus the schema identifier bagwatch.alert.v1 and ordering (oldest first). That is enough to separate it from the token-check and report siblings, though it never explicitly contrasts with watch_report.

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?

Gives concrete operational context: pass next_cursor to page, omit for the start, and a Watch plan key is required. It stops short of naming when to prefer this over watch_report or the token-check siblings, so there is no explicit alternative routing.

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