renew_instance

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

With no annotations, the description must disclose behavior itself. It mentions the payment method (USDC on Base) and that the x402 payment flow is handled automatically, which adds useful context. However, it does not mention prerequisites (e.g., active instance), side effects, or failure behavior, leaving some gaps.

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 two sentences, immediately states the primary action, and includes relevant details without redundancy. Every sentence contributes value.

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 the simple 3-parameter tool and no output schema, the description is fairly complete. It explains what the tool does and how payment is handled. Minor omissions like error handling or prerequisites prevent a perfect score, but it is adequate for usage.

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 100%, so the description does not need to add parameter details. The description mentions the renewal period and instance type implicitly, but the schema already provides clear descriptions. It adds no extra semantic value beyond the schema.

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 clearly states the action (renew), the target resource (existing VPS or Node instance subscription), and the method (using USDC on Base, extending the subscription period). This distinguishes it from sibling tools like create_order or get_instance.

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 implies usage (renew existing subscriptions) but does not provide explicit alternatives or when-not-to-use guidance. For a tool with siblings like create_order and update_custom_name, it would benefit from mentioning that it is for renewals only, not for creating new instances.

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