list_alerts

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

With no annotations, the description must carry the full burden of disclosing behavior. It accurately implies a read-only list operation and states the return format ('JSON string with list of alert rules and their status'), but it does not mention pagination, sorting, or potential edge cases. It is adequate but not fully transparent.

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 extremely concise, with two short sentences and no redundant or filler content. Every phrase contributes useful information about the tool's behavior or parameters.

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?

The description covers the core action, the optional filter, and the return type. Given that an output schema exists, it does not need to specify every output field. It lacks a small amount of context around default behavior (e.g., whether all alert rules are returned when folder_uid is omitted) but is generally complete for a simple list operation.

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 description explains both parameters: connection_name as 'Name of the Grafana connection' and folder_uid as 'Optional folder UID to filter alerts.' This adds meaningful context beyond the bare parameter names in the schema, though it could provide more detail on how to obtain the UID or what 'filter' means exactly.

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's purpose: 'List alert rules, optionally filtered by folder.' It names the resource and the optional filtering behavior, leaving no ambiguity about what the tool does.

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 indicate when to prefer this tool over related siblings such as get_alert_rules_with_state, get_firing_alerts, or get_alert_rule_by_uid. It mentions filtering by folder, but gives no guidance on selection criteria or use cases.

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