create_email_rule

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

Beyond annotations (readOnlyHint=false), the description adds critical behavioral details: the human-approval gate (confirm:true) and the preview behavior with secrets redaction. This fully discloses the operation's nature and safety mechanism.

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 sentences: first states purpose, second explains confirm requirement. Every sentence is essential and front-loaded. No unnecessary 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 covers the core purpose, preview mode, and human-approval need. No output schema exists, but it could mention expected response format or required permissions. Still, it is mostly complete for a simple create tool.

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 100% with descriptive parameter descriptions. The description adds value by explaining the confirm parameter's preview behavior and redaction, which is not in the schema. Baseline 3 is elevated due to this additional context.

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 'Create an Email Routing rule (forward an address to a destination)', using a specific verb and resource. Among siblings like list_email_rules, this tool is uniquely identified for creation. The mention of the confirm gate further clarifies its role.

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 explicitly states when to use this tool (with confirm:true for actual execution) and when to get a preview (without confirm:true). While no alternatives are mentioned, it is the only tool for creating email rules, so the guidance is clear.

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