Buy proxies

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds material context the annotations cannot: the account balance is charged immediately, and estimate_only=true avoids both charging and allocation. It stops short of saying whether a purchase can be reversed or refunded.

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?

Four dense sentences, each carrying distinct information: the charge action, the estimate escape hatch, the geo-selection hierarchy, and the return payload. Nothing is repeated from the schema and the charging behavior 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 money-spending mutation with 9 parameters and no output schema, the description covers the critical risk (immediate charge), the dry-run path, location selection, and the return shape. It omits behavior of auto_renewal and operator, which are the remaining gaps an agent would want.

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 78%, so the schema carries most parameter meaning, but the description adds cross-parameter relationships the schema lacks: country accepts either an ISO code or id_country, and geoid sourced from get_geo_list is the most precise locator. This meaningfully disambiguates three overlapping location parameters.

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?

States a specific verb (buys) and resource (mobile, server or backconnect proxies), and enumerating the proxy types distinguishes it from the sibling buy_residential. An agent can identify the tool's scope without opening the schema.

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?

It gives a useful conditional for estimate_only (quote without charging or allocating) and explains how country/geoid select a location, but it never names an alternative or says when to prefer this over renew_proxies or buy_residential. Usage is implied through parameter branches rather than stated as 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.