aws_terminate_instance

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

Discloses key behaviors: irreversibility, instance-store data loss, EBS volume behavior per DeleteOnTermination flag, and required user confirmation. Annotations are absent, so description carries full burden and meets it well.

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?

Description is concise (3 sentences), front-loaded with the action, and includes essential details without unnecessary words. Every sentence adds value.

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 no output schema, the description adequately explains the destructive effects and data-loss implications. Could mention return status or confirmation in output, but overall sufficient for a dangerous mutation tool.

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% with basic descriptions for instance_id and region. The tool description does not add additional meaning beyond what is already in the schema, so baseline 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 clearly states the tool 'PERMANENTLY terminate an AWS EC2 instance', specifying the verb (terminate), resource (EC2 instance), and permanence, distinguishing it from siblings like stop/reboot.

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?

Includes guidance: 'Reserved for dangerous guard mode' and 'ALWAYS confirm with the user (state the exact instance ID, region, and any data-loss implications) before calling.' Does not explicitly list when not to use or alternatives, but the caution is strong.

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