Create renewal invoice

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

Annotations indicate readOnlyHint=false and destructiveHint=false, so the description adds value by explaining that the tool triggers generation 'now' (manual vs scheduler) and optionally limits to one contract product. This goes beyond the basic read/write hint, though it doesn't disclose potential side effects like idempotency or financial impact.

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?

A single, well-structured sentence that front-loads the primary action and includes the key option. Every word earns its place, no redundancy or filler. Excellent conciseness.

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 tool's simplicity (2 params, no output schema, clear annotations), the description covers the essential behavior and the optional scoping. It does not mention return values or edge cases (e.g., if an invoice already exists), but these are not critical for the core operation. Slightly more detail on expected outcome would improve 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 coverage is 100% and both parameters (contract_id and contract_product_id) have clear descriptions. The description's mention of 'Optionally scope to one contract product' reinforces the contract_product_id parameter but does not add additional meaning beyond the schema. Baseline 3 is appropriate.

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: generate the next recurring/renewal invoice for a contract immediately, rather than waiting for the scheduler. It also indicates an optional scope (contract product), making the tool's purpose specific and distinct from sibling tools like list_invoices or get_invoice.

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 phrase 'instead of waiting for the scheduler' clearly conveys when to use this tool: to trigger an invoice generation manually. It also hints at the alternative (regular scheduled generation) and describes the optional scoping behavior. No explicit exclusions or named alternative tools, but the context is sufficient.

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