iaas_delete_configuration_property

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

The annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered elsewhere. The description adds nothing beyond that — no note on permanence, cascading effects, required permissions, or whether the property must exist first; the endpoint line merely restates the title annotation.

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 purpose line is front-loaded and efficient, but the second line duplicates the annotation title verbatim and earns no place. It is well-sized but one of two lines is redundant.

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 two-parameter, fully-schema-documented delete endpoint with no output schema, this is nearly sufficient. What is missing is the destructive-behavior context (irreversibility, confirmation expectations), which annotations partially cover.

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%, so the id and apiVersion parameters are already documented in the schema. The description contributes no additional semantics about the id (e.g., whether it is a property name or UUID), so the baseline 3 applies.

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 and resource ('Delete a configuration property') and the HTTP route makes the target collection unambiguous. The verb distinguishes it from the sibling read/patch tools (iaas_get_configuration_property, iaas_patch_configuration_property), though it never names them explicitly.

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?

There is no guidance on when to use this versus the sibling get/patch configuration-property tools, no prerequisites, and no warning that the deletion is irreversible. The agent must infer everything from the name and the destructiveHint annotation.

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