delete_an_addressgroup

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

Explicitly declares destructive nature and requires confirmation. Annotations already indicate destructiveHint=true and idempotentHint=true. No contradiction. Adds value with confirmation advice.

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?

Short, front-loaded with destructive indicator. Two sentences plus emoji line. Could be slightly more concise but 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?

For a simple destructive tool with one parameter, description covers purpose, behavior, and user confirmation. No output schema, but return value is implied. Adequate given annotations.

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 covers the single required parameter 'id' with full description. Description does not add extra meaning beyond schema. Baseline 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?

Clearly states it deletes an address group with verb 'delete' and resource 'AddressGroups'. Emoji and HTTP method add clarity. Does not differentiate from sibling delete tools but purpose is unambiguous.

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?

Only guideline is to confirm with user before calling. No context on when to use vs alternatives, prerequisites, or when not to use.

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