List Proxies

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

Without annotations, the description describes return fields but does not disclose non-obvious behaviors like pagination limits, authorization needs, or whether it is read-only. It is adequate but not thorough.

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 concisely state the action and return contents with no extraneous information. Highly efficient.

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 the tool's complexity (12 params, no output schema), the description covers the return fields but omits explicit pagination behavior (limit/offset). Most context is present, with minor gaps.

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?

All 12 parameters have descriptions in the schema (100% coverage), so the baseline is 3. The description adds no extra meaning beyond 'optional filters' and return field summary, which does not exceed the baseline.

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 title and description clearly state the tool lists proxies with optional filters and returns specific details. It is well-distinguished from sibling list tools like list-ips or list-orders.

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?

While it implicitly indicates when to use (need proxy list), it provides no explicit guidance on when to avoid or distinguish from alternatives like list-ips or list-orders.

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