send_template

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only says 'Send Template Message,' which implies a side effect but does not disclose permissions, idempotency, rate limits, or error behavior. This is insufficient for a mutation-like tool.

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 extremely short (three words), but this is under-specification rather than concise efficiency. It omits all substantive content and does not earn its place as a useful description.

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 tool has 8 parameters, a nested language object, no annotations, and no output schema, a one-line description is grossly inadequate. The agent cannot infer how to correctly invoke the tool, making the description contextually incomplete.

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 input schema has 8 parameters (phone, template, namespace, params, language, etc.) with 0% description coverage. The tool description provides no information about what these parameters mean, how they interrelate, or required formats, leaving the agent fully in the dark.

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 'Send Template Message' states the primary action (send) and object (template message) clearly. However, it does not explain what distinguishes a template message from other message types (e.g., send_message, send_button), so it lacks sibling differentiation.

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 the many other send_* siblings, nor any prerequisites (e.g., approved template, user opt-in). There is no mention of alternatives or exclusions.

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