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

Annotations already establish the safe read profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the bar is lower. The description still adds real context: results are scoped to the authenticated user and limited to "active" configurations, and the matching dimensions (keyword, announcement type, ticker, sector) are disclosed.

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, front-loaded with the verb and resource, no filler or restatement of the title. Every clause contributes new information about scope or payload.

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?

An output schema exists, so return-value detail is not required here; the description nonetheless summarizes what comes back. For a zero-parameter read tool the definition is essentially complete, with the only shortfall being the absence of routing guidance against the many 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 the schema has nothing to document and there is no parameter semantics to add. The mention of keyword/type/ticker/sector describes what the stored alerts match on, not call arguments, which is harmless clarification rather than a gap.

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 ("List") and a specific resource ("the authenticated user's announcement alert subscriptions"), and further narrows the payload to "active alert configurations for NZX announcement content." It is clear what the tool does, though it never distinguishes itself from near-neighbors like list_alert_subscriptions or get_keyword_alerts.

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 implies scope ("the authenticated user's") but gives no explicit when-to-use or when-not-to-use guidance, and names no alternative. With siblings such as list_alert_subscriptions, get_keyword_alerts, and the subscribe_* alert tools in the same namespace, an agent gets no signal for choosing among them.

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