Grafana: List Silences

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

Annotations only declare readOnly and openWorld, so the description's addition that expired silences are filtered out by default (and how to include them) is genuine behavioral context an agent would otherwise miss. Pagination/limit behavior is left entirely to the schema.

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?

Two compact sentences with the resource and scope first, then the field list and the expired-silence caveat. The fragmentary opening ('The silences in…') is slightly awkward but wastes no words.

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?

A simple read-only list tool with no output schema, and the description covers sources, returned fields, and the default exclusion behavior — enough for correct invocation. Only the absence of routing guidance against sibling listing tools leaves a gap.

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 limit, search, source and the state enum are already fully documented, including the same 'current/expired/all' semantics. The description adds no format examples or edge-case detail beyond the schema baseline.

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?

Names the concrete resource (silences) and the scope (Grafana's Alertmanager plus every Alertmanager datasource), and enumerates the returned fields, so the agent knows this is a read of silence state rather than alerts or rules. It does not explicitly contrast with siblings like grafana_list_alerts, so it stops short of a 5.

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?

Usage is implied by the return-field list, and the note that expired silences are excluded unless state=expired or all hints at the main selection decision. There is no explicit 'use this when… instead of…' guidance relative to the other list_* tools.

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