Send a poll

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

The description adds behavioral context beyond the openWorldHint annotation by explaining that polls can auto-close via closePeriod/closeDate and that quiz mode requires a correctAnswerIndex. However, it omits side effects like the poll being posted to the peer, irreversibility, or authentication requirements, which limits full transparency.

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 compact and efficient: three sentences, with the core action 'Send a poll' front-loaded, followed by concise parameter guidance. No word is wasted.

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 12 parameters, no output schema, and only an openWorldHint annotation, the description is too sparse to be complete. It covers quiz and closing behavior but ignores return values, error handling, prerequisites, and other significant options like multipleChoice, solution, and anonymous, leaving the agent with significant gaps.

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 only 8%, so the description must compensate. It does clarify key parameters: quiz requires correctAnswerIndex (0-based), closePeriod is in seconds, and closeDate is unix seconds. But it leaves other parameters like multipleChoice, anonymous, replyTo, and accountId without explanatory text, relying on their names.

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 opens with 'Send a poll,' a clear verb+resource statement that directly distinguishes this from sibling tools like vote_poll, close_poll, and get_poll_results. It adds specificity by covering quiz mode and auto-close options, making its purpose unmistakable.

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?

There is no guidance on when to use this tool versus alternatives such as vote_poll or get_poll_results. The description only explains parameter usage (quiz mode, close options) but never addresses tool-selection context or exclusions.

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