wave_send_invoice

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

No annotations provided. The description does not disclose side effects (e.g., whether the invoice status changes to 'sent', email delivery mechanics, or permission requirements). It only says 'send via email' without explaining the process or constraints.

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?

Single sentence, no redundant words. Appropriate length for a straightforward action.

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 simple email action, the description is adequate but could mention prerequisites (e.g., invoice must exist, valid email addresses) or that it may mark the invoice as sent. No output schema means the description should hint at the result, but it does not.

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% for all 5 parameters. The description adds the context that the action is email-sending, but the parameter descriptions in the schema already clearly define each field. No additional meaning beyond schema is provided.

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 'Send an invoice to the customer via email' clearly states the verb (send) and resource (invoice) and specifies the channel (email). It distinguishes from sibling tools like wave_approve_invoice (approve) and wave_mark_invoice_sent (mark as sent without email).

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?

No guidance on when to use this tool versus alternatives like wave_mark_invoice_sent or wave_create_invoice. The description lacks context for prerequisites or exclusions, such as whether the invoice must already be created or if the customer has email.

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