terminate_poll

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

Discloses that poll is closed, participants are notified, final results are visible. Specifies creator-only restriction. Does not mention irreversibility, side effects on ongoing votes, or error conditions. Without annotations, more detail would improve 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?

Four focused sentences with no redundancy. Critical action stated first, followed by logical details. Every sentence contributes essential information.

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?

Covers the main purpose, prerequisites, and parameter selection. Lacks explicit mention of irreversibility, return value, or error handling. Given no output schema, a note on expected outcome (e.g., success confirmation) would improve completeness.

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 has 100% coverage. Description adds value by explaining the source of target_timestamp and poll_id from get_conversation, and the conditional use of recipient vs group_id. This goes beyond schema descriptions.

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 the tool closes (terminates) a poll, stops votes, notifies participants, and shows final results. Distinguishes from related tools like create_poll and vote_poll by specifying the action on existing polls.

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 clear prerequisites: get target_timestamp and poll_id from get_conversation. States only the poll creator can terminate. Explains the choice between recipient and group_id for DM vs group polls. Does not explicitly mention when not to use or alternative tools, but context is sufficient.

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