k8s__get_hpa

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

No annotations are provided, and the description fails to disclose behavioral traits such as read-only safety, required permissions, or side effects. For a tool named 'get', it is likely safe, but the description should explicitly state this.

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?

Single, terse sentence that conveys the core purpose efficiently with no extraneous words. Front-loads the action 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?

For a simple read operation with no output schema, the description mentions key return fields, which is helpful. It is adequate for an agent to understand what the tool does, though it could explicitly state it is read-only.

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?

Input schema covers both parameters with clear descriptions (name and namespace). The description adds context about returned fields (metrics, replicas, conditions) but does not enhance parameter meaning beyond the 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?

Clearly states the action 'Get', resource 'HorizontalPodAutoscaler', and includes relevant details 'metrics, replicas, and conditions'. Distinct from sibling tools which target different Kubernetes resources.

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 is self-explanatory for basic usage, but provides no explicit guidance on when to use this tool versus alternatives like k8s__describe_resource or k8s__get_resource_usage, nor any prerequisites or exclusions.

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