delete_hpa

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

No annotations are provided, so the description must carry the burden. It only states the action 'Delete' which implies destructive behavior, but does not disclose consequences like permanent removal, impact on scaling, or whether confirmation is required. It also does not mention authorization needs or failure modes.

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 extremely concise, a single sentence with no fluff. However, it is so sparse that it borders on under-specification, but for a simple delete operation, it is appropriately sized.

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 the tool has an output schema (likely for status) and only 3 parameters, the description is minimal. It lacks information about the output structure, error handling, or any side effects. For a destructive operation, more context is needed to ensure correct usage, such as confirmation or irreversibility.

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%, so the description should compensate. It does not explain any parameters, but the parameter names (name, cluster, namespace) are self-explanatory and the schema provides defaults for cluster and namespace. The description adds no additional meaning beyond what a user can infer from parameter names.

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 states the action and resource: 'Delete a HorizontalPodAutoscaler.' It is clear but basic, and does not distinguish from siblings like list_hpas or create_hpa beyond the obvious verb difference. It lacks specificity about scope or effects.

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 vs alternatives. It does not mention prerequisites, such as needing the HPA to exist or verifying deletion, nor when it is appropriate to delete an HPA versus scaling it down. The sibling list includes scaling tools, but no differentiation is provided.

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