Enable Auto-Reply Transcription

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

Describes the scoping behavior (contact/phone-scoped, follows JID transitions) and idempotent nature (implied). Annotations already set idempotentHint=true and destructiveHint=false; description adds valuable context beyond these.

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?

Well-structured with summary, then detailed behavior, Args/Returns sections. Slightly verbose with the JID transition explanation, but all sentences add value. Front-loaded main 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?

Completely describes behavior, parameter, and return value. Without output schema, the Returns section covers needed info. Sibling tools context makes it stand out.

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?

Adds meaning beyond schema: specifies format 'Phone number digits only, no @, no spaces' with example, and advises looking up contact first. Schema coverage is 100%, but description enhances usability.

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?

Clearly states 'Enable auto-reply with audio transcription for a contact.' Verb 'enable', specific resource 'auto-reply transcription', and scope 'for a contact' distinguish it from sibling tools like disable, list, etc.

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?

Explicitly notes when to use: 'When the contact sends a voice note, the transcription is sent back as a quoted reply automatically.' Also excludes groups: 'DM only — voice notes in groups are never auto-replied even if a member is flagged.' Advises lookup via whatsapp_list_contacts first.

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