remove_proxy

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

With no annotations provided, the description carries the full burden. It discloses the confirm requirement, response format (accounts still assigned), and the allowed-yet-reported consequence of emptying a pool. It lacks details on permissions, reversibility, or error conditions, but is generally transparent about key behaviors.

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 that are front-loaded with the core action, with no unnecessary words. Every sentence provides essential information.

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?

The description covers the main purpose, required confirm, and response summary. It lacks mention of prerequisites (e.g., pool existence) and error cases, but given the tool's simplicity and the presence of an output schema (though not shown), it is reasonably 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?

Despite 0% schema description coverage, the description adds meaning for the 'confirm' parameter (requires true) and implies the role of 'pool' and 'proxy_url' through the action. However, it does not detail input formats, constraints, or the effect of confirm=false, leaving param semantics somewhat underspecified.

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 the action ('remove a proxy URL from a pool'), using a specific verb and resource that distinguishes it from sibling tools like 'add_proxy' and 'test_proxy'.

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 notes the requirement for confirm=true and explains the behavior when emptying a pool, providing clear context for when to use this tool. However, it does not specify when not to use it or mention alternatives beyond the sibling list.

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