create-template

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

The annotations already declare destructiveHint=true, indicating this is a write operation. The description adds minimal behavioral context beyond that - it confirms creation but doesn't specify what happens on success/failure, whether templates are immediately usable, or any permissions required. No contradiction with annotations exists.

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 a single, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized for a creation tool with good schema documentation and gets straight to the point.

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 creation tool with destructiveHint annotation and no output schema, the description is minimally adequate. It identifies the resource type but doesn't explain what an email template entails in this system, how it's used, or what the creation result looks like. The combination of basic description and annotations provides the essentials but leaves contextual gaps.

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?

With 100% schema description coverage, all parameters are documented in the schema. The description adds no additional parameter information beyond what's already in the schema descriptions. The baseline score of 3 reflects adequate but not enhanced parameter 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 the verb ('create') and resource ('email template'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'update-template' beyond the obvious verb difference, nor does it specify what distinguishes a template from other email-related resources in the system.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (like needing to be logged in), when to choose this over 'update-template' for existing templates, or how it relates to email-sending tools like 'send-email' or 'send-sandbox-email'.

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