meta-preview_email

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

With no annotations, the description carries full burden. It discloses the authorization requirement ('Admin only'), recipient constraint ('whitelisted test address'), and purpose (preview, no real users). It does not mention error handling or side effects, but for a simple email preview, this is sufficient.

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 two concise sentences, front-loaded with 'Admin only.' Every word serves a purpose with 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?

Given the tool's simplicity (no output schema, 3 params), the description combined with schema covers purpose, authorization, usage, and parameter details. It could mention the return value, but the overall completeness is good.

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?

Input schema has 100% description coverage, so the schema already documents parameters well. The description adds no additional parameter meaning beyond 'Admin only' context. Baseline 3 is appropriate.

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 action: 'Sends an email template preview to a whitelisted test address.' It specifies the verb (sends), resource (email template preview), and context (admin only, for iterating on designs). This distinct purpose is well-differentiated from sibling meta tools.

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 indicates 'Admin only' and 'Use for iterating on email designs without creating real users.' This tells the agent when to use the tool and the key precondition (whitelist). It does not list alternatives, but the context is clear enough for a preview tool.

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