Send Email via Salesforce

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

The description adds substantial behavioral nuance beyond the annotations. It discloses that emails are sent from the running user's address, respect org deliverability settings, and that saveAsActivity defaults to true (creating an activity record). It also warns about daily email limits, which are not surfaced in the annotations or schema.

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 is well-organized: a concise opening sentence, a bulleted list of key parameters, and a note about limits. Every sentence earns its place, and there is no redundancy.

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 covers core behavior, parameter semantics, and important limitations (deliverability, email limits, mass email alternative). It doesn't describe the return value, but since there is no output schema and this is a side-effectful action, that omission is acceptable.

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?

The schema already provides 100% parameter coverage, but the description clarifies semantics: htmlBody takes precedence over body, templateName replaces body text, and whatId/whoId link the email to records/person records. This adds valuable context beyond the schema's brief descriptions.

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 tool's function: 'Sends an email from Salesforce using the emailSimple invocable action.' This specifies the verb (send), resource (email via Salesforce), and mechanism (emailSimple invocable action), distinguishing it from sibling tools like sf_create_email_template or sf_create_email_alert.

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 gives explicit when-not guidance: 'Mass emails should use list email features instead.' This implies the tool is for individual/transactional emails. It doesn't name a specific alternative tool, but the direction is clear and helpful.

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