Submit WhatsApp template for moderation

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

Annotations only include openWorldHint, offering no behavioral disclosure. The description implies a state-changing action but does not explain consequences like the template becoming pending, being locked for edits, or requiring additional permissions.

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 and concise in length, but it is under-specified. It states the core purpose but lacks necessary detail, so it doesn't fully 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?

With no output schema, an unexplored nested object parameter, and no behavioral context, the description is severely incomplete. It fails to clarify what moderation entails, what the body should contain, or what response to expect.

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%, and the description provides no information about the 'id' or 'body' parameters. The nested 'body' object is entirely unexplained, leaving the agent to guess its structure and 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 the tool submits a WABA template for moderation, using a specific verb and resource. It distinguishes from sibling template tools like create/update/delete by indicating a moderation submission action, though it doesn't explicitly name alternatives.

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 other template tools, nor does it mention any prerequisites or context. It simply restates the action without explaining the approval workflow or alternative paths.

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