whatsapp_send_document

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

No annotations provided, and description gives minimal behavioral context. Does not disclose side effects, required permissions, success/failure behavior, or rate limits. The one-line description does little to explain what happens when sending.

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?

Highly concise: two sentences, front-loads the action. No wasted words, every part earns its place.

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 11 parameters and no output schema, the description is far too brief. Ignores many optional parameters (caption, mentions, etc.) and does not explain the expected behavior beyond the basic action.

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?

Description clarifies that 'data' and 'url' are alternatives and 'filename' is required. With schema coverage at 55%, this adds some value but not enough to fully compensate for the other parameters left unexplained.

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 the action 'Send a document file' and the resource. Distinguishes from siblings like whatsapp_send_image via naming and scope.

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?

Provides explicit guidance on providing either base64 data or a URL, and that filename is required. However, no when/why to choose this over other sending tools beyond name.

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