androidapi_send_whatsapp

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

Annotations already provide readOnlyHint=false, openWorldHint=true, destructiveHint=false. The description adds minimal behavioral context beyond the schema (e.g., mentions attachments but not side effects, rate limits, or required account setup). With annotations present, additional disclosure is expected but lacking.

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 efficiently conveys the core functionality with no wasted words. It is front-loaded and easy to parse.

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 11 parameters, 3 required, and no output schema, the description is too brief. It omits context like the need to obtain an account ID from androidapi_get_wa_accounts, the optional nature of priority/shortener, or typical usage flow. The schema covers details, but the description should provide higher-level guidance.

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 coverage is 100%, so the baseline is 3. The description does not add meaning beyond the schema descriptions; it merely summarizes the supported types already detailed in parameter enums and descriptions.

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 action ('send a single WhatsApp message to one recipient') and lists supported types (text, media, document). However, it does not explicitly differentiate from the bulk version (androidapi_send_whatsapp_bulk), though the word 'single' implies the distinction.

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 implies when to use (single messages) but provides no explicit guidance on when not to use or alternatives. The sibling tool for bulk sending exists but is not mentioned, leaving the agent to infer the context.

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