recurring_invoices_bulk_issue_now

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

Annotations already declare it is a non-read-only, non-destructive, non-idempotent operation, so the description's added value is the non-obvious side-effect note: 'Does not update the nextIssuanceDate.' That is exactly the kind of caveat an agent cannot get from structured fields. It still leaves unstated whether created invoices are drafts or issued, and how partial failures across the id array are handled.

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 short sentences, no filler, with the core action front-loaded and the caveat last. Every sentence carries distinct 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?

For a non-idempotent bulk mutation with no output schema, the description should say what comes back (per-id results? count of invoices created?) and whether inactive templates are skipped or error. The nextIssuanceDate caveat is helpful but the outcome contract is left open.

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%: the ids array documents the 1-100 UUID range and companyId documents the default override. The description adds nothing about the parameters, so baseline 3 applies since the schema does the work.

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?

States a specific verb and resource: 'generate invoices from multiple recurring invoice templates', with 'Immediately' and 'multiple' distinguishing it from the singular recurring_invoices_issue_now sibling. It never names that sibling explicitly, so the differentiation is implied by wording rather than stated.

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?

'Useful for triggering generation outside the normal schedule' gives a clear condition for reaching for this tool rather than waiting for the scheduler. No exclusions or named alternatives, so an agent must infer that recurring_invoices_issue_now covers the single-template case.

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