get-alerts

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

Since no annotations are provided, the description must carry the full burden of behavioral disclosure. It states the read operation and provides severity mappings, but does not mention pagination, default return format, sorting, or any side effects. This is a significant gap for a tool with no annotation safety signals.

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 exactly two sentences, front-loaded with the main action, and provides the severity mapping in the second sentence without any fluff. Every word 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?

For a simple list tool with fully documented optional parameters, the description is largely complete. It lacks explicit details on pagination or response structure, but the schema covers parameter semantics, and the tool's purpose is clear. Without an output schema, some behavioral details would help, but the minimal nature of the tool makes this acceptable.

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 schema already documents all three parameters with 100% coverage, so the baseline is 3. The description goes beyond by enumerating severity value meanings (6=Critical, 5=Major, etc.), which directly helps users construct filter expressions and adds value not present in 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 starts with 'Retrieve all alerts', a specific verb and resource, and clarifies 'optionally filtered'. This clearly distinguishes it from the singular 'get-alert' tool and other CRUD operations on 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 plural 'all alerts' and the option to filter imply a list/query use case, and the sibling tools show this is the primary list operation. However, there is no explicit mention of alternatives or when not to use this tool, so it is clear but not fully explicit.

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