List alerts

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

The description adds no behavioral details beyond the annotations. It mentions the endpoint and a return list, but does not disclose pagination behavior, filtering limitations, or other runtime traits. The annotations already cover read-only and idempotent safety.

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 concise sentences and front-loads the core purpose. The endpoint reference is minimal and not redundant.

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 list tool with rich schema descriptions and safety annotations, the description is minimally adequate. It lacks explicit mention of pagination or return format, but the schema covers parameters. Given no output schema, the description could be slightly more informative, but it is not incomplete for the tool's complexity.

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 input schema fully documents all five parameters with descriptions and examples, so the description does not need to add parameter details. It adds no additional semantic meaning beyond the schema.

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 uses the specific verb 'List' with the resource 'alerts' and states 'Returns a list of your alerts,' clearly identifying the tool's function. It is distinct from siblings like showAlert (single alert) and resolveAlert (mutation).

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?

No guidance is provided on when to use this tool versus alternatives such as showAlert or resolveAlert. The description only states what it does, not when to choose it or when to avoid it.

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