List Alerts

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

readOnlyHint=true already establishes this is a safe read, so the description's job is to add context beyond that. It mentions closed vs. open alerts, but says nothing about result ordering, default page size, or how nextId continues a paged read — the mechanics an agent needs for repeat calls.

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 purpose sentence and use-when bullets are front-loaded and scannable, and the examples are compact. Slight redundancy between the 'including closed alerts' bullet and the withClosed example, but nothing wasteful.

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 read-only list tool with no output schema and fully documented parameters, the description covers what to call it for and how to toggle closed alerts. Pagination behavior via nextId is the one gap, though the schema carries it.

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 100%, so all three parameters are already documented. The example list_alerts(withClosed=true) usefully demonstrates that the default excludes resolved alerts, but limit and nextId semantics are left entirely to the schema. Baseline 3 applies.

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 — 'Retrieve alerts from Mackerel' — and the bullets make clear it returns alert collections rather than a single alert. It does not explicitly contrast with siblings like get_alert or get_alert_logs, which an agent could confuse with it.

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 'USE THIS TOOL WHEN USERS' block gives concrete trigger conditions (active alerts, including closed alerts) and the examples show both default and withClosed invocations. There is no explicit when-not guidance or named alternative for single-alert lookups.

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