createTextMessageTemplate

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

No annotations are available, and the description merely says 'Create', implying mutation. It does not disclose permissions, idempotency, side effects, or any constraints beyond the input schema.

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 sentence, which is concise but lacks structure. It conveys the core purpose without wasting words, but does not include any contextual or behavioral 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?

Given the low complexity, 100% schema coverage, and lack of output schema or annotations, the description is minimally adequate. It explains the basic action but does not cover what happens after creation or any constraints.

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?

The schema covers 100% of parameters with descriptions ('Template name', 'Message body'), but these descriptions are minimal and do not add significant meaning beyond the parameter names. Baseline of 3 is appropriate as the schema does the primary documentation work.

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 states the verb 'Create' and the resource 'text message template', clearly identifying the action. However, it does not differentiate this from the sibling tool 'createTemplate', which could be confused as a generic template creator.

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?

No guidance is provided on when to use this tool versus alternatives like 'createTemplate' or 'createTextMessage'. There is no mention of prerequisites or typical use cases.

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