list_alert_subscriptions

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

With no annotations provided, the description carries the full burden. It discloses that the tool reads authenticated user's subscriptions, describes the filtering parameters and delivery details, and indicates safe read-only behavior. However, it omits potential pagination, rate limits, or result ordering.

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 description is two well-structured sentences. The first sentence delivers the core purpose immediately. The second sentence packs relevant details without redundancy. Every element earns its place.

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?

Given no parameters and no output schema, the description covers the tool's function (listing subscriptions), filtering capabilities, and delivery format. It mentions the Enterprise tier requirement. It lacks information on return format or pagination, but is largely complete for a listing tool.

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 has 0 parameters and schema coverage 100%. Per guidelines, 0 params baseline is 4. The description adds context about what the tool lists, but no parameter semantics are needed.

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 tool lists all alert subscriptions for the authenticated user, specifying the verb 'list' and resource 'alert subscriptions'. It provides extensive details on filtering criteria (tickers, sectors, signal types, anomaly categories, severity) and delivery method (webhook with HMAC-SHA256), which distinguishes it from sibling tools that retrieve individual data items.

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 does not provide explicit guidance on when to use this tool versus alternatives, such as create or modify subscription tools. It mentions 'Enterprise tier required' as a prerequisite but lacks context on when not to use or comparisons to sibling tools.

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