iaas_delete_azure_cloud_account

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the description need not restate the safety profile, but it adds essentially nothing beyond them — no mention of what happens to dependent resources, whether deletion requires the account to be detached first, or what authorization is needed. The only extra content is the raw HTTP endpoint.

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 first line duplicates the second line and the annotation title, so the description wastes roughly a third of its length on repetition. What remains is short and front-loaded, but the redundancy is notable in a three-line description.

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 destructive, provider-scoped delete with no output schema, the description omits the things an agent most needs: consequences of deletion, preconditions, and how to recover the correct identifier. The annotations carry the safety signal, but the description does little to complete the picture.

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 both `id` and `apiVersion` are already documented in the input schema. The description's phrase 'with a given id' merely restates the schema and adds no format, sourcing, or lookup guidance (e.g., how to obtain the id via iaas_get_azure_cloud_accounts). 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?

States a specific verb and resource ('Delete an Azure Cloud Account') and names the provider, which distinguishes it from generic siblings like iaas_delete_cloud_account and provider-specific ones like iaas_delete_aws_cloud_account. It does not, however, explain how it differs behaviorally from those siblings beyond the provider name.

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 explicit guidance on when to use this tool versus alternatives, no prerequisites (e.g., the account must be unassociated/no deployments), and no warning or confirmation guidance despite the operation being irreversible in practice. Usage is only implied by the tool name and the 'with a given id' phrase.

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