create_poll

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

With no annotations, the description states it creates and sends a poll, returns a timestamp, and that terminate_poll stops voting. Does not mention any destructive consequences or permissions, but behavior is fairly clear for a creation tool.

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?

Four concise sentences with no fluff. Front-loads purpose, then conditions, return value, and related tool. Every sentence adds value.

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?

Adequately complete given no output schema: mentions return timestamp and references sibling tools for next steps. Covers constraints and usage context sufficiently.

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 covers all 5 parameters (100% coverage). Description adds value by clarifying mutual exclusivity of recipient/group_id, explaining multi_select behavior, and reinforcing minimum options requirement.

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 it creates and sends a poll, specifies verb and resource. Distinguishes from siblings vote_poll and terminate_poll by mentioning the timestamp needed for those.

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 when to use (creation), conditions (at least 2 options, multi_select flag), and parameter requirements (exactly one of recipient or group_id). Does not explicitly mention when not to use, but does enough.

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