firing_alerts

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

The description includes a '[READ]' tag, which is useful since no annotations are provided. It also notes that output is grouped by severity. However, it does not disclose other behavioral aspects such as permissions, cost, or exact return format, so it only partially carries the burden.

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 an Args block. It is front-loaded with the [READ] tag and purpose, and every line adds value without waste.

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 read-only tool with one optional parameter and no output schema, the description covers the essential purpose and parameter semantics and gives a hint about output grouping. It could be more explicit about the exact return structure, but the tool's simplicity makes it adequate.

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 only defines the target parameter as a string or null. The description adds meaning by explaining that it is a 'Prometheus target name from config' and that it can be omitted for the default, providing useful context 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 clearly states the tool's function: it reads currently firing Prometheus rule alerts and groups them by severity. This distinguishes it from sibling tools like alertmanager_alerts (which may show all alerts) and pending_alerts (which show pending 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 usage is implied: use this tool to retrieve currently firing Prometheus rule alerts. However, it does not explicitly mention when to prefer this over related tools such as alertmanager_alerts or pending_alerts, nor does it provide exclusion criteria.

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