Create Workflow Email Alert

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

Annotations already convey that this is a non-destructive write operation (readOnlyHint=false, destructiveHint=false, idempotentHint=true). The description adds minimal behavioral context beyond the tool's function, such as not stating permissions needed or side effects. It does not contradict the annotations.

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 front-load the primary action and include essential context. Every sentence earns its place with no filler or repetition.

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 create tool with 9 well-documented parameters and no output schema, the description gives a clear purpose and usage context. It could mention prerequisites or post-creation effects, but the schema and annotations fill most gaps. The context is sufficient for an agent to select and use the tool correctly.

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 provides 100% coverage of all 9 parameters with descriptions. The description redundantly mentions 'email template' and 'recipients (owner, creator, users, roles, or custom email addresses)' which partially maps to parameters but does not add new meaning beyond the schema's own documentation.

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 'Creates a Workflow Email Alert action' with a specific verb and resource. It also clarifies that it can be triggered by Flows, Approval Processes, or Workflow Rules, distinguishing it from other create tools like sf_create_workflow_rule or sf_create_email_template.

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 phrase 'Use when you need to send notification emails as part of automation' gives clear context for when to use this tool. It does not explicitly name alternative tools or list exclusions, but the automation-focused wording helps differentiate from direct email sending tools like sf_send_email.

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