alertmanager_list_silences

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

Annotations already declare readOnlyHint=true and destructiveHint=false, indicating a safe read operation. The description adds context that a silenced alert is invisible in Prometheus /alerts, which is useful behavioral insight. However, it does not mention potential edge cases like pagination or rate limits.

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 well-structured with a clear opening statement, the API endpoint, return details, usage guidance, and examples. Every sentence adds value, and it is appropriately brief for the tool's complexity.

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?

Given the tool's simplicity (2 optional params, no required, has output schema), the description covers purpose, usage, and return values adequately. However, the lack of parameter semantics creates a notable gap, making it slightly incomplete.

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 description coverage is 0%, meaning the parameters 'instance' and 'instances' are undocumented in the schema. The description fails to explain these optional parameters or how they affect the query, leaving the agent without guidance on filtering by instance.

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 explicitly states 'List all silences from Alertmanager' with a clear verb and resource. It differentiates from sibling tool alertmanager_list_alerts by noting when not to use it, ensuring no confusion.

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?

Provides explicit when-to-use scenarios with concrete examples ('Is the HighCPU alert silenced?') and a clear don't-use case ('Don't use when: You want active firing alerts (call alertmanager_list_alerts)'). This guides the agent effectively.

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