nex_ip_renew

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

The annotations already state destructiveHint=true and idempotentHint=false, and the description adds important operational details: renewal charges the balance at current server price, order groups may partially succeed, and unclear outcomes require reconciliation before retry. That materially improves the agent's understanding of risk beyond the annotations.

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?

The description is compact and front-loaded: it starts with the core renewal action and ID scope, then adds billing/retry constraints. Every sentence adds operational value with no filler.

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 destructive/billing risk, partial success, and retry policy, which is substantial for a destructive tool. However, with no output schema and 0% schema parameter descriptions, the missing meaning of the required duration parameter remains a notable gap for correct invocation.

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 description coverage is 0% for 2 required parameters. The description clarifies that "items" means local proxy IDs from nex_proxy_list rather than order/upstream IDs, but it says nothing about the required "duration" parameter, such as its unit or how it affects renewal length or price.

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 states a specific verb and resource: "Renew local proxy IDs from nex_proxy_list," and explicitly distinguishes those IDs from "order or upstream IDs." This gives an agent a clear action and object without needing to inspect sibling schemas.

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?

It gives explicit usage boundaries: call directly when the task needs it, a price inquiry is not a purchase request, replace unusable proxies rather than renewing them again, reconcile before retry if unclear, and cap attempts at 3 per resource flow. These are actionable when/when-not rules and alternatives.

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