Delete environment

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds critical context: deletion fails with 409 if the environment is not empty, and offers alternatives. This supplements the annotations well, though the core destructiveness is already indicated.

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 concise: four sentences covering action, condition, alternatives, and API call. No redundant information; each 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?

For a simple delete tool with one parameter and no output schema, the description fully covers: action, precondition (empty), error case (409), alternatives, and API endpoint. No missing information needed for proper use.

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 only parameter 'environmentId' is a simple string. With 0% schema coverage, the description does not elaborate on its format or meaning beyond 'the provided ID'. However, the purpose is obvious from the tool name and description, so this is adequate but not exceptional.

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 deletes an environment by ID, using the verb 'Delete environment'. It distinguishes this from sibling tools like render_create_environment and render_retrieve_environment by specifying the action and resource.

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 explicitly states when to use (to delete an empty environment) and when not to use (if non-empty), providing alternatives such as moving/deleting resources or using the Dashboard. This clearly guides the agent on correct invocation.

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