End poll

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

The description states it closes a poll and finalizes results, but does not disclose what happens if the poll is not owned by the bot, if the poll has already ended, or if the action is irreversible. Annotations indicate non-destructive, but the description lacks behavioral depth beyond the core action.

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 a single sentence that efficiently states the tool's purpose and scope, with no unnecessary words. It front-loads the critical action and resource.

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 has 3 parameters, no output schema, and no annotations beyond readOnly/destructive hints, the description is somewhat sparse. It does not explain return values, errors, or prerequisites beyond implying ownership. For a simple action it is adequate but incomplete.

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 67%: channel and guild have brief descriptions, but message_id lacks any description. The tool description does not clarify the purpose of message_id or any other parameter, relying on the schema's limited info. This leaves ambiguity for the agent.

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 specifies the verb 'Close' and resource 'one of the bot's own polls', with the additional context 'early and finalize the results', distinguishing it from other poll-related tools like create_poll or get_poll_results.

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 implies usage when a bot wants to end its own poll early, but it does not explicitly state when not to use (e.g., if the poll has already ended) or mention alternative methods (e.g., waiting for the poll to end naturally).

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