send_poll

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

No annotations provided and the description is minimal. It fails to disclose that this tool sends an interactive WhatsApp poll, requires an Evolution API instance, or any side effects (e.g., message sent, network dependency).

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 very concise (one sentence), but this brevity comes at the cost of informative content. For a tool with 9 parameters and nested objects, more structure would be beneficial.

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 complexity (9 params, no annotations, no output schema), the description is severely incomplete. The agent lacks context on tool behavior, return values, and operational requirements, leading to potential misinvocation.

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 89%, so the schema already documents most parameters. The description adds no extra meaning beyond 'poll message', which is adequate but not helpful for understanding parameter roles.

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) and the resource (poll message). It differentiates from siblings like send_plain_text or send_media, though it could be more specific about the poll's interactive nature.

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 send_list or send_buttons. The description omits prerequisites, when-not-to-use, or examples, leaving the agent without decision support.

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