get_whatsapp_template

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

The description adds the behavioral context that this tool retrieves (read) a template's details, which aligns with the readOnlyHint annotation. However, it does not disclose any additional behavioral traits such as error handling, authorization needs, or rate limits. The annotation already indicates it's a safe read operation, so the description's contribution is minimal.

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 that is concise and front-loaded with the verb and resource. Every word is essential, and there is no extraneous information. It efficiently communicates the tool's purpose.

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 a simple tool with one parameter and no output schema, the description is adequate but not complete. It does not describe the return value, such as the structure of the template details. Considering the low complexity, it is minimally sufficient but could be more informative.

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 0% description coverage for the parameter template_uuid. The description adds the meaning that it is a UUID identifier, which is valuable but still minimal. It does not describe the format, constraints, or source of the UUID. The schema provides minLength:1 but no further description, so the description partially compensates.

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 clearly states the verb (obtiene detalle) and the resource (plantilla de WhatsApp) and the identifier (UUID). It distinguishes the tool from sibling tools like list_whatsapp_templates and send_template by specifying it retrieves a single template's details.

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 alternatives. It does not mention prerequisites, limitations, or when not to use it. The context of retrieving a specific template by UUID is implied but not explicitly stated.

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