order_proxy

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

With no annotations, the description fully discloses that this operation spends money and is irreversible, requires confirm to execute, and shares scopes with VM/k8s mutations. The refusal behavior when confirm is false/omitted is also explained.

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?

Three concise sentences cover action, scope, parameter groups, and spending warning. Information is front-loaded with no redundancy. Every sentence serves a purpose.

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 key behavioral aspects and parameter groups. Lacks mention of return value (e.g., order ID), but given the complexity and lack of output schema, the description is still thorough enough for an AI agent to use correctly.

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 coverage is 100%, but the description adds significant value by grouping parameters into two shapes (ISP vs GB bucket), explaining defaults, and associating each shape with its specific parameters, which aids correct parameter selection.

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 action ('Order a new residential proxy plan and CHARGE the account'), identifies two plan shapes, and distinguishes from sibling tools like get_proxy_catalog or cancel_proxy by emphasizing the financial transaction.

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 guidance on required scope ('services:write') and the critical confirm parameter ('pass confirm:true only after the user approves the plan and cost'). It also references discovery tools (get_proxy_catalog, list_regions) for options, though it does not explicitly state when not to use this tool.

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