Contract Testing: Delete Environment

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the description adds no new behavioral information. It does not disclose whether deletion is permanent, whether associated deployments or releases are removed, or whether there are any side effects beyond removing the environment itself.

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 short and front-loaded with the core action, and the toolset label aids orientation. The parameter section duplicates schema information, but this is minor given the tool's simplicity.

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 single-parameter deletion tool, the description is minimally sufficient: the agent knows what to delete and by what identifier. However, given that this is a destructive operation and there is no output schema, some mention of consequences or the irreversibility of the deletion would improve completeness.

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 100%, and the sole parameter environmentId is fully described in both the schema and the description as 'UUID of the environment'. The description adds no meaning beyond the schema, so the 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 states a specific verb ('Delete'), a concrete resource ('an environment'), and the identifying key ('by UUID'). This clearly distinguishes it from sibling tools like contract-testing_create_environment, contract-testing_update_environment, and contract-testing_get_environment without requiring schema inspection.

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 gives no guidance on when to use this tool versus alternatives such as contract-testing_update_environment or contract-testing_list_environments. It also does not mention any prerequisites, safety checks, or conditions under which deletion is appropriate. Usage is only implied by the tool name and title.

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