delete_stack

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

The description only conveys that the tool destroys a resource, which is inherently destructive. However, it does not disclose any behavioral details such as whether the deletion is permanent, whether it affects dependent resources, or any required permissions. Since no annotations are provided, the description carries the full burden but fails to add meaningful context.

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 a single concise sentence with no redundant words. It efficiently communicates the core 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 deletion tool with one required parameter and no output schema, the description is minimally adequate. However, it lacks context about post-deletion effects (e.g., reversibility, impact on other resources), which would be helpful for an agent to fully understand the tool's consequences.

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 coverage is 100%, so the description adds no additional meaning beyond the input schema. The parameter 'stack_id' is described in the schema as 'ID del stack a eliminar', which is clear. Baseline score of 3 is appropriate as the schema itself provides adequate documentation.

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 'Elimina un stack de Komodo' which directly translates to 'Delete a Komodo stack'. The verb 'elimina' (delete) and the resource 'stack' are specific, distinguishing it from sibling tools that delete other resources like alerters, builds, etc.

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 (e.g., delete_stack vs. stop_stack or undeploy). There is no mention of prerequisites, conditions, or when deletion is appropriate.

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