delete_traffic_shaper

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

Annotations already mark this as destructive with readOnlyHint=false, so the description doesn't need to state that it's a write operation. It adds the explicit warning that the operation is irreversible, which is a meaningful behavioral trait beyond a generic destructive flag. However, it does not mention side effects on dependent resources or the confirm/dry-run flow (though the schema covers those).

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 exactly two sentences: the first delivers the core action, the second a necessary warning. There is no redundant phrasing or unnecessary context, and the structure is front-loaded.

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 operation, the description is adequate: it states the action and warns about irreversibility, while the schema fully explains parameters and the output schema presumably documents return values. It does not cover when to use this versus sibling tools, but that gap is relatively minor given the tool's simplicity and the strength of the structured data.

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 input schema documents all four parameters with descriptions, achieving 100% coverage. The description mentions only the 'by ID' aspect, which maps to the shaper_id parameter, but doesn't add further semantic detail. The schema's descriptions for confirm and dry_run already provide safety-gate and preview semantics, so the description offers no extra value.

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 the specific action ('Delete') and target resource ('traffic shaper') with the scope of deletion by ID. It is clear but does not explicitly compare with related tools like update_traffic_shaper, so it doesn't fully differentiate in-text.

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 when-to-use or in what scenario this is the appropriate tool is offered. The irreversibility warning is a caution but not guidance about when to choose deletion over updating or alternatives. The needed prerequisite of obtaining the ID via search appears in the schema, not the description.

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