cancel_proxy

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

Discloses irreversible nature with confirm requirement, prepaid behavior (no refund, no upstream teardown), and scope sharing with VM/k8s mutations. Exceeds the destructiveHint annotation with specific behavioral details.

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?

Concise yet comprehensive; front-loaded with purpose, then covers scope, semantics, and precautions. Every sentence adds value, no fluff.

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 aspects: purpose, prerequisites, behavior, and irreversibility. Lacks mention of return value or error handling, but not essential given no output schema and clear operational description.

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 significant meaning beyond schema: explains cancel parameter default and undo behavior, describes confirm's role as explicit user approval gate. With 100% schema coverage, description still provides essential context.

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 it cancels any proxy service (ISP, GB Residential, mobile) with a specific verb and resource, distinguishing it from sibling tools like cancel_service or renew_proxy.

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?

Explicitly explains prepaid semantics, when to use (at period end), and how cancel parameter works (default true to cancel, false to undo). Mentions required scope and source of id, providing clear when-to-use guidance.

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