List available proxy locations

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

Discloses caching behavior (60s server-side, 5 min client-side). Annotations (readOnlyHint, openWorldHint) align with description. No contradictions.

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?

Two sentences conveying all essential info: return data, use cases, caching. 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 return data, usage contexts, required geoid for buy_proxy, caching, and filtering. Complete given optional single parameter and no output schema.

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?

The single parameter 'country' is described in both schema and description with similar detail. Description adds usage context (filter by ISO code) but does not significantly expand beyond schema.

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?

Explicitly states it returns all geo-locations with specific fields (geoid, caption, ISO, free-modem count) for proxy availability. Clearly distinguishes from siblings like list_proxies by focusing on locations.

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 use cases: recommend location, validate before buy_proxy/change_geo, filter by country. Mentions geoid needed for buy_proxy, linking to sibling tools.

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