Send Sale Invoice

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

Annotations already declare destructiveHint=true, and the description reinforces this with 'DESTRUCTIVE — sends real documents', adding context about the irreversible nature of sending. This goes beyond the annotation by clarifying what gets destroyed (real documents sent to recipients). No other behavioral traits are needed given the simple action.

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?

Two concise sentences: first states the action, second warns about destructiveness. No wasted words. Front-loads the core 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?

Adequate but incomplete: missing info on response/return value (no output schema), prerequisites (e.g., invoice must exist and possibly be confirmed), and error cases. Given the tool's simplicity and the rich annotation context, it's minimally viable but could provide more operational context.

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 baseline is 3. The description does not add any additional meaning to the parameters beyond what the schema already provides. It mentions 'via e-invoice or email', which aligns with the boolean params but does not enhance their understanding.

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?

Clearly states the tool sends a sales invoice via e-invoice or email. The verb 'send' plus 'sale invoice' differentiates from sibling tools like confirm, delete, or list invoices. The mention of specific methods (e-invoice or email) adds clarity.

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. There is no mention of prerequisites (e.g., invoice must be in a certain state) or cases where another tool (like confirm_sale_invoice) might be more appropriate. The description is purely functional.

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