komodo_delete_deployment

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

With no annotations provided, the description carries the full behavioral burden. 'Delete' implies a destructive, presumably irreversible mutation, but the description does not state whether the operation is reversible, whether it requires elevated auth, whether it cascades to related resources, or what happens on failure. It only notes a 'Deletion confirmation' return, which the output schema already covers.

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 text is short and front-loaded with the purpose, and the Args/Returns structure is tidy. However, the brevity reflects under-specification rather than disciplined conciseness, and the Returns line is redundant with the existing output schema.

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 single-parameter tool with zero annotation coverage, the description is too thin: it omits irreversibility, auth/permission needs, and failure behavior. The presence of an output schema excuses it from explaining return values, but not from the behavioral context a delete operation requires.

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 single parameter has no type/format detail in the schema, so the description must compensate. 'id: Deployment ID' adds only marginal meaning beyond the parameter name, without specifying whether it is numeric vs string, a slug vs UUID, or where the agent obtains it.

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 a specific verb (Delete) and resource (deployment), which cleanly distinguishes it from the sibling delete_build, delete_stack, and delete_server tools as well as from create/update/get/list variants. It is clear but offers no explicit sibling differentiation beyond the resource name embedded in the tool name.

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 guidance on when to use this tool versus alternatives (e.g., stop_deployment vs delete_deployment), no preconditions, and no note about what state the deployment must be in. An agent is left to infer entirely.

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