get_whatsapp_template

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds 'Fetches data. Makes no changes' which reinforces annotations but doesn't add new behavioral insights beyond the endpoint path.

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 reasonably concise but includes redundant elements like the endpoint URL and emoji. Could be tightened to a single sentence without losing meaning.

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 simplicity of the operation (single required param, read-only, no nested objects, no output schema), the description adequately covers what the tool does and its single input. It doesn't describe the return format, but that is common for standard CRUD tools.

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?

Only one parameter id is required, and the description explicitly explains it is the template Id. Despite 0% schema coverage, the description compensates by stating 'Gets a WhatsApp Template by Id', clarifying the parameter's purpose.

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 'Get WhatsApp Template' and 'Gets a WhatsApp Template by Id', indicating a specific read operation. It implicitly differentiates from sibling tools like list_whatsapp_templates which lists all templates, but lacks explicit 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?

No guidance on when to use this tool versus alternatives like list_whatsapp_templates or send_a_whatsapp_template_message. The agent must infer usage from context.

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