pbs_traffic_control_delete

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

With no annotations, the description covers key behaviors: dry-run by default, confirm flag to commit, mutation level (LOW), and post-deletion effect (backups unthrottled). It mentions 'Smoke-confirm' for success response. Lacks details on permissions or error handling but compensates for annotation absence.

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 extremely concise—four sentences covering purpose, effect, recovery, execution instruction, and response shape. No redundant information; each sentence earns its place.

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?

Given the presence of an output schema, the description effectively covers the delete operation's lifecycle: dry-run, commit, effects, and recovery. It does not address error cases or permissions, but for a simple delete tool with these cues, it is adequately complete.

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?

Only 33% schema description coverage. The description adds context for 'name' via the HTTP path and explains 'confirm' usage. However, it does not elaborate on 'name' format or 'proximo_target' beyond the schema. The schema provides a description for proximo_target, but the description does not add 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 clearly states the tool removes a PBS traffic-control rule, explicitly distinguishes from upsert by noting recoverability, and provides the verb 'remove'. It is specific and differentiates from sibling tools like pbs_traffic_control_upsert.

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 explains when to use (to remove a bandwidth-limit rule), mentions dry-run behavior and the need for confirm=True to execute. It also notes recovery via upsert, providing context for decision-making. No explicit when-not-to-use, but adequate for a delete tool.

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