List my proxies

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

Beyond annotations (readOnlyHint, openWorldHint), the description reveals that expired proxies are already dropped server-side but the active_only filter provides an extra client-side check. It also discloses the returned fields (host, port, login, password, geo, operator, expiration).

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?

The description is concise—three sentences each serving a distinct purpose: what it returns, when to use it, and parameter details. No redundant or unclear language.

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?

Given no output schema, the description sufficiently explains the return content. It covers all three parameters, usage context, and a dependency (get_country_list). No gaps for an agent to select and invoke 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 context: the type parameter lists enums, id_country is numeric and requires get_country_list for conversion, and active_only defaults to true with explanation. This adds value beyond the schema alone.

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?

Description clearly states the tool returns all proxies owned by the user with full connection details, distinguishing it from sibling tools like get_proxy_status or get_balance. It explicitly says to use this first when the user asks about 'my proxies'.

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?

The description provides explicit guidance: use this first for any query about 'my proxies', to find a specific proxy, or to obtain a proxy_id for other tools. It also advises using get_country_list for ISO codes, offering a clear alternative.

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