compare_kubernetes_clusters

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

No annotations are provided, so the description carries full burden. It mentions the tool compares costs and efficiency and depends on an environment variable, but does not disclose whether it is read-only, what actions it performs, or any side effects. Moderate transparency.

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 three sentences plus examples, with no wasted words. It front-loads the primary purpose and uses bullet-like examples for clarity.

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 description provides usage context, it lacks details about the output format, specific metrics compared, or prerequisites. Given no output schema, more explanation of what the comparison returns would be beneficial.

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 input schema has no parameters (100% coverage). The description adds meaning by explaining that configuration is done via an environment variable (K8S_CONTEXTS), which is not part of the schema but essential for usage.

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 compares costs and efficiency across all configured Kubernetes clusters, using specific verbs and scope. It distinguishes from sibling tools like get_kubernetes_costs which focus on a single cluster.

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 explains it's useful for multi-cluster setups (prod vs staging, region vs region) and mentions configuration via K8S_CONTEXTS. It gives example queries, providing clear context for when to use this tool.

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