create_template

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

Annotations indicate readOnlyHint=false (write operation), but description adds minimal behavioral context beyond creation. Does not disclose details like required authentication, potential duplication behavior, or that additional properties are not allowed despite openWorldHint.

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: first states purpose, second provides actionable usage pattern. No redundant or extra words. Front-loaded with key information.

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?

Covers essential usage (creation with placeholders) and links to sending. Does not specify return value (likely template ID), but for a creation tool this is acceptable. With no output schema, a minor gap remains.

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 covers all parameters with descriptions. Description adds value by explaining the placeholder syntax ({{variable}}) and how to use them with send_email, enhancing understanding beyond raw schema.

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?

Description clearly states 'Create a reusable email template.' Specifies verb (create) and resource (email template), and distinguishes from siblings by mentioning {{variable}} placeholders and linking to send_email.

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?

Gives explicit guidance on using placeholders and how to pass values via send_email's templateData. Implies appropriate context for template creation. Does not explicitly state when not to use or list alternatives like duplicate_template.

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