create_template

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

With no annotations, the description carries the full behavioral disclosure burden. It does disclose the POST endpoint and the templating behavior (subject/html/text with {{ variables }} and optional variable definitions), but it says nothing about authentication, duplicate-name behavior, validation, or response side effects, leaving meaningful gaps.

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 short clauses, front-loads the action and resource, and every phrase adds information: endpoint, supported fields, and variable behavior. There is no filler or 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?

For an 8-parameter creation tool with no annotations and no output schema, the description omits meaningful context: no usage guidance, no behavior on conflicts, no response expectations, and several parameters are only name-based. It is not complete enough for an agent to invoke with full confidence based solely on the description.

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 description coverage is only 38%, so the description needs to compensate. It usefully adds the {{ variables }} injection syntax and identifies subject/html/text as the supported content fields, but it leaves from, alias, and reply_to semantics to bare property names in the 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?

The description names the exact action ('Create') and resource ('reusable email template') and gives the explicit endpoint, so an agent can distinguish this from update_template, duplicate_template, and list_templates without inspecting schemas. 'Reusable' adds useful scope beyond a generic create action.

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 verb 'create' and the endpoint imply this tool is for new templates, but the description does not explicitly state when to use it over update_template or duplicate_template, nor does it mention exclusions or prerequisites. Usage guidance is only implied, not stated.

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