recurring_invoices_issue_now

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

The description adds important behavioral context beyond the annotations by explaining that scheduled generation is bypassed and that nextIssuanceDate is not updated. It does not contradict the non-readOnly, non-idempotent annotations, and the caveat about nextIssuanceDate is especially useful for an agent predicting side effects.

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 tight sentences front-load the core action, then add use cases and an important side-effect caveat. Every sentence contributes relevant information without 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 simple two-parameter mutation tool with annotations covering safety and idempotency, the description is mostly complete. The main remaining gap is that it does not describe what the tool returns, which matters because no output schema is provided.

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?

The input schema already has 100% description coverage for both parameters. The description reinforces that the uuid identifies a recurring invoice template but adds no parameter-level detail beyond what the schema provides, so the baseline of 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 states a specific action: manually trigger immediate invoice generation from a recurring invoice template, bypassing scheduled generation. It clearly distinguishes the tool from scheduled generation, though it does not explicitly contrast with the sibling recurring_invoices_bulk_issue_now.

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?

It gives concrete use cases: testing configurations and creating one-off invoices. It also clarifies the bypass behavior, but does not explicitly state when to choose this over recurring_invoices_bulk_issue_now.

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