delete-environment

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

With no annotations provided, the description fully discloses critical behaviors: permanent deletion, irreversible operation, asynchronous execution, 'all associated resources' affected, and the --allow-write flag requirement. It also states the return value, exceeding expectations for a destructive tool.

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 well-organized with a short summary, behavioral notes, and a clear Args/Returns structure. Every sentence adds useful context without unnecessary padding.

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 delete tool with no output schema, the description covers the operation's scope (all resources), irreversibility, async nature, required flag, and return confirmation. This is complete for the tool's complexity.

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 schema already documents all three parameters with descriptions, and the description merely echoes 'override' for region and profile. No new semantic meaning is added beyond the schema's high coverage, so the baseline 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 'Delete an MWAA environment' and elaborates with 'Permanently deletes the specified MWAA environment and all associated resources.' The verb 'delete' and resource 'MWAA environment' are specific and clearly distinguish this from sibling tools like create-environment, update-environment, and get-environment.

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?

The description conveys that this is for permanent, irreversible deletion and requires the --allow-write flag, establishing clear context for when it should be used. However, it does not explicitly name alternative tools or exclusion conditions (e.g., 'for temporary disable, use update-environment'), so it stops short of a full 5.

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