k8s_pod_status

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

With no annotations, the description carries full burden. It does disclose two useful traits: the output is 'bounded' (no unbounded dumps) and only 'approved' clusters/namespaces are accepted, which signals a governance constraint. It still omits whether this is strictly read-only, what permissions are needed, and what 'bounded' concretely caps.

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?

A single front-loaded sentence with the verb first and zero filler. It is tight, though the brevity contributes to the gaps in the other dimensions rather than being purely efficient.

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?

An output schema exists, so return values need not be explained. However, for a tool with two undocumented parameters and no annotations, the description leaves an agent without enough to know when to invoke it or how to populate its arguments.

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% and the two parameters (cluster, namespace) have only defaults, no semantics. The description references both indirectly via 'approved cluster and namespace' but adds no format, expected values, or default behavior, so it fails to compensate for the empty schema.

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 names a specific verb and resource ('Return a bounded pod-status summary') scoped to a cluster and namespace, so the agent knows what it produces. It does not distinguish itself from siblings like host_health or slow_probe, leaving the agent to infer the boundary between pod-level and host-level diagnostics.

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?

There is no statement of when to choose this tool over host_health, slow_probe, or search_runbooks. The phrase 'approved cluster and namespace' hints at an access precondition but never spells out a usage scenario or exclusion.

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