deployment_delete

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action is deletion but lacks critical details: whether this is destructive (likely yes, but not confirmed), if it requires specific Kubernetes RBAC permissions, what happens to associated resources (e.g., pods, services), or error handling (e.g., if deployment doesn't exist). The return statement is vague ('Status of the deletion operation') without specifying format or possible outcomes.

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 efficiently structured with a clear purpose statement followed by parameter and return sections. Every sentence serves a purpose: the first states the action, the next three define parameters, and the last describes returns. It's front-loaded with the core functionality, though the return statement could be more specific.

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 destructive operation like deletion with no annotations and no output schema, the description is incomplete. It lacks crucial context: safety warnings, permission requirements, impact on related resources, and detailed return value expectations. Given the complexity and risk of deleting Kubernetes deployments, more behavioral and operational guidance is needed.

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 description explicitly lists and briefly defines all three parameters ('context_name', 'namespace', 'name'), adding meaningful context beyond the schema which has 0% description coverage and only provides titles. This compensates well for the schema's lack of documentation, though it doesn't elaborate on parameter formats (e.g., namespace naming conventions) or examples.

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 action ('Delete') and resource ('a Deployment from the specified namespace'), making the purpose immediately understandable. It distinguishes from siblings like 'deployment_create' or 'deployment_update' by specifying deletion, though it doesn't explicitly contrast with other deletion tools like 'namespace_delete' or 'pod_delete'.

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 is provided on when to use this tool versus alternatives. While the description implies it's for deleting deployments, it doesn't mention prerequisites (e.g., needing proper permissions), consequences (e.g., pods being terminated), or when to choose other deletion tools like 'namespace_delete' for broader cleanup.

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