Create poll

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

The annotations only indicate readOnlyHint=false and destructiveHint=false, so the description carries some burden. It adds that the poll is a "native Discord poll" and specifies answer/duration limits, but it does not disclose potential side effects (e.g., message sent to channel, permission requirements, error conditions). This is acceptable but minimal.

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?

A single sentence, front-loaded with the verb "Post," and every word contributes meaning. It efficiently communicates the primary action and essential constraints without bloat.

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 tool's moderate complexity (7 parameters, no output schema), the description captures the core purpose and key limits. It could mention the return value or permission requirements, but the schema and context cover most details. For a creation tool, the description is adequately complete.

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?

The schema already covers 71% of parameters with descriptions. The description adds semantic meaning by clarifying the role of key parameters: the question is a poll question, answers are choices (2-10), and duration is capped at 32 days. This goes beyond the schema's raw constraints.

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 tool's purpose: "Post a native Discord poll" with specific constraints on question, answers (2-10), and duration (up to 32 days). This distinguishes it from sibling tools like get_poll_results and end_poll, which handle retrieval and termination.

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 context of when to use this tool is clear — to create and post a poll in Discord. However, it does not explicitly mention when not to use it or provide alternative tool names (e.g., send_message or create_event), so it lacks explicit exclusions.

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