discord_create_poll

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the agent knows this is a non-destructive write to an external system. The description adds only the 'native' qualifier (vs. a message-based poll) and the answer-count range, which the schema already states; permission requirements and result behavior are unaddressed.

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 front-loaded sentence with zero filler and the key constraint in parentheses. It is tight, though arguably too sparse for a 5-parameter create tool.

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 annotations covering the safety profile and no output schema required, the minimum is met, and three of five parameters are at least nominally documented. Still missing: required permissions, what the call returns (poll message), and any behavior around duration limits.

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 60%, so the description should compensate, but it only restates the 2-10 answer constraint already in the schema and implies the channel target. duration_hours and allow_multiselect receive no clarification in the description, leaving their semantics entirely to the partial schema.

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?

Clear verb (Post) plus specific resource (native Discord poll) and scope (2-10 answers, in a channel). An agent can distinguish this from discord_send_message without opening the schema, though no sibling is named explicitly.

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 description states what the tool does but gives no when-to-use guidance, no indication of when a regular discord_send_message is preferable, and no prerequisites or permission context. Usage must be inferred from the name alone.

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