terminate_poll

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

Discloses participant notification, final result visibility, and creator-only constraint. With no annotations, description carries full burden; adequately transparent about effects and restrictions.

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?

Three sentences, front-loaded with purpose, each sentence adds necessary detail. No wasted words.

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 5 parameters, no output schema, and no annotations, the description covers purpose, prerequisites, constraints, and parameter usage adequately. Might omit explanation of return value, but likely void.

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 100%, so baseline is 3. Description adds value by explaining where to get parameters (from original poll message) and the mutually exclusive choice between recipient and group_id.

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 'Close (terminate) a poll you created, stopping any further votes.' Distinguishes from sibling tools like create_poll and vote_poll by specifying termination action and scope (you created).

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 prerequisites: get target_timestamp and poll_id from get_conversation, and clarifies creator-only restriction. Lacks explicit when-not-to-use vs alternatives, but covers key usage context.

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