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

Annotations declare destructiveHint=true and idempotentHint=false, which are non-obvious for a create operation and are never explained or reconciled in the description. The merge-tag syntax is useful content guidance but says nothing about whether repeated calls create duplicate templates, whether the name must be unique, or what the call returns. The description neither contradicts nor meaningfully augments the annotation profile.

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 short sentences, purpose front-loaded, no filler. The trailing 'per-recipient variables' is an undefined term that adds ambiguity rather than precision, which keeps it from a 5.

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?

There is no output schema, so the description is the only source for return behavior, yet it never says whether the created template's ID is returned or whether the template is immediately usable in send_message/create_automation. For a mutation tool with a surprising destructive hint, key facts an agent needs before calling are missing.

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 0%, so the schema documents only types and max lengths. The description compensates partially by explaining the merge-tag syntax that is valid inside `body`, but it says nothing about `name` semantics (uniqueness, reuse across templates, effect on lookup). Partial compensation for a two-parameter tool.

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 verb 'Save' plus the resource 'message template' make the operation unambiguous, and the name create_template aligns. It does not explicitly contrast with update_template or state whether it creates a new template versus overwriting an existing one, but an agent can identify the operation without opening the schema.

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?

There is no guidance on when to use this tool rather than update_template (the obvious sibling for modifying an existing template) or when a template is the right choice over send_message with inline content. Usage is only implied by the name.

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