list_alerting_rules

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

The description only identifies the resource type and adds 'with rule group count'. It does not disclose if it is read-only, requires specific permissions, handles pagination, or any other behavioral traits. Since no annotations are provided, the description carries the full burden but falls short.

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 a single concise sentence that front-loads the core purpose. Every word adds value; no unnecessary information.

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?

Despite having an output schema, the description omits basic usage context like optional filtering by cluster/namespace. It is minimally adequate for a simple list tool but lacks completeness in explaining the parameters and return behavior.

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 0% and the description provides no information about the two optional parameters (cluster, namespace). Their purpose (likely filtering) is not described, leaving the agent to guess their semantics.

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 lists PrometheusRules (a specific Kubernetes CRD) and includes a unique detail: rule group count. This distinguishes it from siblings like list_alerts (active alerts) and get_alert_details (single alert).

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?

No guidance on when to use this tool versus alternatives. Siblings like list_alerts exist for active alerts, but the description does not clarify when to choose this tool over them. No exclusions or prerequisites are mentioned.

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