recurring_invoices_issue_now

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

No annotations are provided, so the description carries the full burden. It discloses that it bypasses scheduled generation and importantly states 'Does not update the nextIssuanceDate' — a meaningful side-effect disclosure that helps the agent understand consequences. It doesn't mention whether the action is reversible or requires confirmation, but the key behavioral traits are disclosed.

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 sentences with zero wasted words. It front-loads the action, explains the use case, and discloses a key side-effect. Every sentence earns its place with no redundancy.

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 tool with 2 well-documented parameters, no output schema, and no nested objects, this description is complete. It covers purpose, use case, and the critical side-effect of not updating nextIssuanceDate. It could mention return values or what the generated invoice looks like, but for a straightforward trigger action this is sufficient.

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 both parameters (uuid and companyId) are already fully documented in the schema. The description adds context about the uuid being a 'recurring invoice template' but doesn't add meaning to companyId beyond what the schema provides. Baseline 3 is appropriate since the schema does the heavy lifting.

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 verb+resource ('Manually trigger immediate invoice generation from a recurring invoice template') and clearly distinguishes itself from scheduled generation. It also clarifies it's for testing or one-off invoices, differentiating it from sibling tools like recurring_invoices_update, recurring_invoices_toggle, and 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?

The description explicitly states when to use it ('useful for testing configurations or creating one-off invoices') and clarifies a key behavioral exclusion ('bypassing the scheduled generation'). While it doesn't name alternative tools, the sibling set includes recurring_invoices_bulk_issue_now which is implicitly distinct. It doesn't explicitly state when NOT to use it, but the purpose statement is clear enough for proper selection.

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