add_ip_to_vps

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

Annotations only indicate readOnly=false and destructive=false, so the description carries the burden of disclosing the purchase transaction. It adds critical behavioral context: the charge is ongoing, not one-time, and confirmation is required. This is valuable context beyond what the annotations provide.

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 front-load the main action, then deliver the cost warning, the confirmation requirement, and the alternative tool. Every sentence earns its place with no filler or repetition.

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?

For a mutating purchase tool with no output schema, the description covers the action, target, pricing, confirmation requirement, and an alternative. It does not describe response shape or error behavior, but those are less critical than the cost and confirmation details it does provide.

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%, but the description adds meaning to confirm by saying it must be true and points to check_available_ips for price. It does not explicitly describe vps_id beyond 'this VPS,' though the parameter name makes it reasonably clear. This is adequate but not comprehensive.

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 opens with 'Purchase and attach a brand-new IP address directly to this VPS,' giving a specific verb, resource, and scope. It clearly differentiates from attach_ip by emphasizing 'brand-new' and from a generic purchase by saying 'directly to this VPS.'

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 warns about the ongoing monthly charge, directs the agent to check_available_ips for pricing and hourly-rate conversion, and states that confirm=true is required. It also gives an explicit alternative: 'To attach an IP you already own instead, see attach_ip.'

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