Contract Testing: Delete Environment

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

The description says 'Delete' while annotations claim readOnlyHint=true and destructiveHint=false. This is a direct contradiction, leaving the agent uncertain about the tool's actual behavior. No additional behavioral traits are disclosed.

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 very concise, with only two lines. It front-loads the purpose and parameter. No unnecessary words.

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 the tool is a delete operation, the description should mention irreversibility, consequences, or reference the toolset. It only states the bare action. The contradiction with annotations makes it incomplete and misleading for an agent.

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?

Only one parameter environmentId, described as 'UUID of the environment' in both description and schema. Schema coverage is 100%, so the description adds no extra meaning beyond what the schema provides.

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 action 'Delete an environment by UUID', specifying verb and resource. It distinguishes from sibling tools like create/get/update/list. However, the contradiction with annotations (readOnlyHint=true, destructiveHint=false) may confuse the agent about the actual operation.

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 explicit guidance on when to use or not use this tool. The context implies it's for deleting an environment, but no prerequisites, alternatives, or consequences are mentioned. Basic implied usage.

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