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

Goes well beyond the destructiveHint/idempotentHint annotations by stating the send is immediate and cannot be undone, that the sender must be on a verified domain, the 5 MB total size ceiling, and that a template supplies subject and sender name. These are operational constraints the annotations alone do not convey.

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?

Front-loads the highest-stakes fact (irreversible send), then the content-shape choice, then size limit, then the confirm protocol, and closes with the endpoint. Every sentence carries an actionable constraint with no filler.

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?

Covers the branching, prerequisites, limits, and safety protocol for an 11-parameter mutation tool with no output schema. The one omission is what a successful call returns (e.g., a message/submission id), which matters for follow-up verbs like enginemailer_check_transactional_report_export.

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?

Adds real meaning for the trickiest parameters: the template_id vs subject/content_html tradeoff, sender_email's verified-domain requirement, and the attachment size limit. The remaining gap is that cc/bcc, campaign_name, sender_name, and substitution_tags get no treatment in the description, though the schema documents most of them (64% coverage).

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 (submits/sends) and resource (a single transactional email to one recipient), and the emphasis on ONE email distinguishes it from the campaign-oriented siblings. An agent can tell immediately this is the single-message path rather than enginemailer_send_campaign.

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?

Explicitly defines the pre-send protocol: confirm recipient and text with the user first, set confirm to true only after approval. It also gives the content branch (subject + content_html OR template_id) and the prerequisite of a verified sender domain, so the agent knows the conditions for a valid call.

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