List proxies

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

Annotations already declare readOnlyHint=true, so the description doesn't need to repeat safety. It adds value by noting the returned proxy_uuid is intended for binding, which gives insight into the output structure. No contradictory behavior is disclosed.

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 with no unnecessary words. The first sentence states the action, and the second gives a practical follow-up. Well-structured and 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?

This is a simple read-only list tool with schema and annotations covering most context. The description implies the response contains proxy_uuid, which is enough to complete the binding workflow. It could be slightly more explicit about the response format, but given the simplicity, it is sufficiently complete.

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 75%, which is moderate. The description doesn't delve into parameter meanings but the schema already documents most properties (tab, page, page_size). The keyword parameter lacks a schema description, yet the description doesn't compensate. The main focus is on output usage rather than input parameters, so a baseline score of 3 is appropriate.

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 'List saved proxies' with a specific verb and resource, and distinguishes itself from sibling proxy tools (add_proxies, delete_proxy, check_proxy, list_proxy_regions). It also provides a concrete next step (using proxy_uuid for binding), which clarifies the tool's role in the workflow.

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 explicitly says to use the returned proxy_uuid to bind a proxy to a profile via create_profile or quick_update_profile, giving a clear context for when this tool is useful. It does not mention exclusions or alternatives, but the primary use case is well articulated.

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