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

With no annotations, the description carries the full burden and does so: it discloses the sender identity, that the send is immediate and externally visible, that it is logged in the SaaS admin, and that it is SUPERADMIN ONLY. It also flags the prompt-injection risk around recipient sourcing, which is exactly the kind of behavioral context annotations would otherwise have to supply.

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 delivery effect and the draft_report contrast are front-loaded, followed by the attachment hint, the permission gate, and the security constraint. Every sentence adds a distinct decision-relevant fact; the caps emphasis is deliberate rather than noise.

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 9-parameter outbound-email tool with no output schema, the description covers sender, logging, permissions, attachment mechanics, and the security constraint on recipients. It stops short of saying what the call returns (e.g. message id) or what happens on failure, which are the only remaining gaps.

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 coverage is 89%, so the schema already documents each parameter, and the baseline would be 3. The description adds cross-parameter meaning beyond the schema: the attachment is a PDF passed as base64, and the 'to' value has a provenance constraint (operator instruction, never site content).

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 specific verb and resource ('Send an email NOW from Site Doctor's own address') and adds the secondary effect ('log it in the SaaS admin'). It explicitly distinguishes itself from the sibling draft_report by contrasting delivery with mere drafting.

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?

Gives explicit when-to-use ('actually DELIVER a report or note to a client, colleague or account owner'), names the alternative and what it does differently ('unlike draft_report, which only drafts'), and adds an exclusion rule: do not send if the recipient is not operator-confirmed. Nothing is left to inference.

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