renew_proxy

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

Discloses financial impact: creates a charged renewal invoice, settled from credit/bonus, and bulk discounts. With no annotations, this adequately warns about mutation and cost, though lacks details on failure modes.

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?

Efficiently packed with critical info in a few sentences. Front-loaded with purpose, then scope, then financial warning, then parameter details. No wasted words.

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?

Covers key aspects: required scope, source for id, financial impact, confirm guard, bulk options. No output schema but return value not essential for action tool. Could mention result type, but overall 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?

All three parameters described in schema (100% coverage). Description adds value: id source, confirm semantics, periods with discount details, enhancing schema info.

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?

Clearly states the verb 'renew' and resource 'proxy service' for another billing term. Distinguishes from siblings like renew_service, order_proxy, set_proxy_auto_renew, and cancel_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?

Explicitly mentions required scope (services:write), source for id (list_proxies), and when to use confirm flag (only after user approval). Does not explicitly contrast with alternatives but provides sufficient context.

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