renew_service

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

Discloses that the operation spends money by generating/settling a renewal invoice from balance. No annotations provided, so description fully carries the burden. Highlights irreversibility via user approval requirement.

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?

Three concise sentences. First states purpose, second covers scope and side effect, third gives parameter guidance. No redundant information.

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 all critical aspects for a financial operation: purpose, prerequisites (scope, user approval, source of ID), and side effect (spends money). No output schema needed; description is self-sufficient for safe 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 coverage is 100% with good descriptions for both parameters. Description adds minimal value beyond schema (e.g., reinforcing confirm warning and service_id source). Does not introduce new parameter details.

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 it ensures a renewal invoice exists for a service and renews the current term. It distinguishes from sibling tools like set_service_autorenew by explicitly mentioning invoice generation and spending.

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 states required scope (services:write), user approval prerequisite, and source of service_id (list_services). Tells when to pass confirm:true and implies not to use without explicit approval.

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