topup_proxy

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

No annotations are present, so the description carries the full burden. It discloses a quote-then-commit process and the pricing formula (per_gb * additional_gb). This goes beyond the schema and provides useful behavioral context, though it does not mention reversibility or permissions.

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 concise sentences, front-loaded with the primary purpose. Every clause adds value—purpose, process, and pricing—with no unnecessary 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 adequately covers the main aspects: what it does, how pricing works, and the quote-then-commit nature. No output schema exists, so return values are not required, but the description could mention prerequisites or side effects for even better completeness.

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%, so the description must compensate. It clearly explains the role of additional_gb in the pricing formula and implies how proxy_id is used ('shared proxy plan'). However, it does not explicitly define proxy_id, leaving it to inference.

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?

Clear verb+resource: 'Add more data to a shared proxy plan'. Differentiates from siblings like purchase_proxy or renew_proxy by specifying the action (add data) and the resource (shared proxy plan).

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?

States when to use: to add more data to a shared proxy plan. Does not explicitly mention alternatives or when not to use, but the context is clear enough for an agent to select this tool over purchase_proxy or renew_proxy.

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