delete_proxy_request

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

Adds beyond destructiveHint annotation by stating IRREVERSIBLE and immediate endpoint termination. Also explains confirm parameter behavior.

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?

Every sentence serves a purpose: action, scope, irreversibility, parameter guidance. No filler.

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?

Covers all critical context: scope, irreversibility, prerequisites, and confirm usage. Complete for a destructive tool.

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?

Adds value beyond schema by specifying data sources (list_proxies, list_proxy_requests) and confirm semantics (omit/false refuses).

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 a proxy-request from a GB Residential bucket, specifies required scope, and distinguishes from other proxy-request operations.

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?

Provides explicit when-to-use guidance: scope services:write, GB Residential only, and prerequisites for id and reqId. Does not explicitly contrast with other deletion tools, but context is clear.

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