list_prometheus_rules

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

With no annotations, the description should disclose behavioral details. It fails to mention that namespace defaults to 'default' and does not explain the role of cluster_alias. The read-only nature is implied by 'List' but not explicitly stated.

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, efficient sentence with no wasted words, front-loading the verb and resource.

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?

While the operation is simple and an output schema exists, the description omits key context about the default namespace value and cluster_alias semantics. This could lead an agent to mis-invoke the tool when targeting a specific cluster or namespace.

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 provides no descriptions for the parameters, and the tool description adds minimal insight. It references 'in a namespace' but does not explain the namespace default or the cluster_alias parameter, which the agent would need to correctly invoke the tool.

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 specifies the verb 'List', the resource 'PrometheusRules', and clarifies they are alerting/recording rules, scoped to a namespace. This distinguishes it from sibling get_prometheus_rule which fetches a single rule.

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 clearly indicates this tool is for enumerating all PrometheusRules in a namespace, which is the typical use case. However, it does not explicitly mention alternatives or provide when-not-to-use guidance, though for a list tool the use case is unambiguous.

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