k8s__list_deployments

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

With no annotations, the description should disclose behavioral traits. While 'list' implies a read-only operation, there is no explicit statement about safety, side effects, or permissions. The description only hints at the return content, not behavior.

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 very short and front-loaded but is a noun phrase rather than a complete sentence. While concise, it omits important details, making it under-specified rather than efficiently informative.

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?

Given no output schema or annotations, the description should fully explain the tool's scope. It mentions return data but does not address namespace optionality, default behavior (e.g., all namespaces), pagination, or ordering, leaving gaps for agent decision-making.

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 single parameter 'namespace' is not mentioned in the description. With 0% schema description coverage, the description must compensate but fails to explain the parameter's role or filtering behavior.

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 indicates the tool lists deployments and specifies included information (replica counts, rollout health), distinguishing it from other list tools like list_pods or list_services. However, it lacks an explicit verb and could be slightly more precise.

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 (e.g., list_pods for pods, describe_resource for details). Does not clarify namespace filtering or default behavior, leaving the agent to infer.

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