send_invoice_by_email

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

The description adds crucial context 'SENDS REAL EMAIL — irreversible' beyond the annotations, which declare destructiveHint=false. This warns the agent about the irreversible nature of sending real emails, despite annotations suggesting it is not destructive.

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?

The description consists of a single sentence that conveys the core action and an important warning, with no redundant words.

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?

The description is too brief for a tool with 6 parameters and no output schema. It fails to explain key parameters like recipients, receipt, and from, or how the email sending behaves (e.g., who gets it, if a copy is saved).

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?

Since schema description coverage is 100%, the description does not need to add param details. The description offers no additional meaning beyond the schema, meeting the baseline.

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 clearly states the action 'Sends specified invoice by email' and emphasizes the irreversibility, distinguishing it from similar tools like send_invoice_by_post and other email sending tools.

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?

The description does not explicitly state when to use this tool versus alternatives like send_invoice_by_post or other email senders, nor does it provide prerequisites or exclusions. The 'irreversible' warning offers some implicit guidance.

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