create_invoice

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does add value beyond the name by disclosing the key side effect: a buyer checkout URL is generated. But it does not disclose what state the invoice enters, auth requirements, reversibility, or what the response contains — meaningful gaps for a mutation 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 14-word sentence with zero wasted words. The primary action is front-loaded, and the additional buyer-checkout-URL outcome is stated in a second clause without 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?

With 8 parameters, no output schema, and no annotations, the description is on the thinner side. The schema fully documents parameters, and the description hints at the primary deliverable (checkout URL), but it never states what the tool returns (invoice ID? URL field?), nor any prerequisites. An agent would likely need to inspect actual return behavior to safely chain this with downstream steps.

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 the schema already documents all 8 parameters, including defaults (currency, expires_in_minutes) and fallback behavior (business_id). The description adds no parameter-level detail, but with complete schema coverage the baseline of 3 applies.

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 ('create') with a clear resource ('payment checkout invoice') and adds a distinct outcome ('generate the buyer checkout URL') not obvious from the name alone. It cleanly differentiates from sibling tools like list_invoices, get_invoice_details, and delete_invoice by making the creation + checkout intent explicit.

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?

Usage context is implied by the verb 'create' — the agent can infer it is the right choice over list/get/delete invoice siblings when a new checkout is needed. However, there is no explicit when-to-use guidance, no exclusions, and no mention of prerequisites such as requiring an active business or API keys.

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