Generate subscription invoice

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

Annotations already flag this as destructive, non-idempotent, and open-world, so the safety profile is known. The description adds nothing beyond that: it does not say an invoice is a persistent/billable artifact, that a private file is written, or that 'confirm' gates the action — missing context that matters for a destructive tool.

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 short sentence, front-loaded with the action, so it is easy to scan. The trailing clause 'with given parameters' is redundant padding that earns no place.

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 12-parameter destructive write operation with no output schema, the description should at least hint at required billing inputs and the generated file/URL result. It omits all of that, leaving the agent to reconstruct behavior entirely from the schema and annotations.

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% across all 12 parameters, so the schema carries the semantics and a 3 is the baseline. The phrase 'with given parameters' adds no meaning at all about which fields are required billing details versus optional metadata.

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 and resource ('Generates a new invoice for the given subscription'), so an agent can tell what the tool produces. It does not distinguish itself from close siblings such as generate_order_invoice or refund_subscription_invoice, and 'with given parameters' is filler rather than scope.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g., the confirm flag, the required output_file), and no routing to alternatives like generate_order_invoice or get_subscription_invoice. The agent must infer everything from the name.

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