delete_stack

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

No annotations are provided, and the description does not disclose behavioral traits beyond the action 'delete'. It does not mention whether this operation is irreversible, requires permissions, or affects other parts of the analysis (e.g., decompilation). For a destructive tool, this is insufficient.

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 at three words, which is efficient but could be expanded to include important context without becoming verbose. It earns its place but does not fully utilize available space.

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 that no annotations are provided and the output schema exists but is not described, the description does not specify return values or side effects. For a destructive operation with two required parameters, more information is needed to ensure correct invocation.

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 input schema documents both parameters with descriptions for addr, name, and instance_id, covering 50% of the schema according to context. The description adds no new information about parameters beyond what is in the schema, so a baseline score of 3 is appropriate.

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 'Delete stack vars' clearly specifies the action (delete) and the resource (stack variables), distinguishing it from siblings like 'declare_stack' which likely creates them. However, 'stack vars' could be more explicit about whether it refers to local variables or stack frames, but it is sufficiently clear.

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 such as 'declare_stack' or 'stack_frame'. The description lacks context for appropriate usage, such as prerequisites or conditions for deletion.

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