Generate order invoice

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

Annotations already declare destructiveHint=true, idempotentHint=false, openWorldHint=true, and readOnlyHint=false, giving the safety profile. The description adds nothing beyond that: it does not explain the destructive implication, the confirm gate, or that output_file must be a new non-overwriting file. It does not contradict the annotations, but it contributes no behavioral context of its own.

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 that is front-loaded with the action and resource. It is efficient, though the redundant "with given attributes" clause is dead weight that serves no purpose.

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, 7-required destructive write with no output schema, the description is far too thin. It omits that output_file is mandatory and non-overwriting, what confirm guards, and how this differs from generate_subscription_invoice — all critical for correct invocation.

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 every parameter is already documented in the schema, establishing the baseline of 3. The description adds no parameter meaning beyond "with given attributes," which tells the agent nothing new about id, confirm, output_file, or the address fields.

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 clear verb+resource ("Generates a new invoice") scoped to "the given order," which implicitly distinguishes it from the sibling generate_subscription_invoice. However, the trailing phrase "with given attributes" is filler and it never names the alternative explicitly, so differentiation is only implicit rather than deliberate.

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 prerequisites, and no mention of when-not-to-use or the sibling generate_subscription_invoice. The agent must infer entirely from the tool name that this is for order invoices rather than subscription invoices.

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