Change proxy login and password

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

Goes well beyond the annotations (which already flag destructive, non-idempotent, open-world) by disclosing key behavior: missing credentials generate random ones, the same pair is applied to every proxy, and old clients stop connecting. This adds valuable context about side effects and defaults, though it omits auth/rate-limit details.

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?

Four tightly written sentences, front-loaded with the primary action and followed by important behavioral details. Every sentence earns its place without redundancy.

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 a mutation tool with three parameters, no output schema, and rich annotations, the description covers purpose, default behavior, side effects, and return value. It is nearly complete, missing only explicit guidance on alternatives and edge cases like permission requirements.

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?

With only 33% schema description coverage, the description compensates by explaining that login/password are optional and what happens when they are omitted, plus that the same pair applies to all proxies. It adds meaningful semantics beyond the schema's pattern constraints.

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?

States a specific verb and resource: 'Sets a new login and password on one or more proxies.' This clearly distinguishes it from sibling tools that manage IPs, geo, or traffic, though it does not explicitly name alternatives. The core purpose is unambiguous.

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 a concrete scenario ('for example after credentials leaked'), which implies when to use it. However, it does not specify when not to use it or how it differs from related tools like update_proxy_settings or rotate_ip. Usage is implied rather than fully guided.

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