send_poll

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

With no annotations, the description does well to disclose behavioral traits: auto-close timing, public voting, quiz mode with correct answer and solution. However, it omits potential side effects (e.g., permission requirements, notification behavior). Slight gap.

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 concise given the complexity: a one-line summary followed by bullet-point parameter explanations. Every sentence adds value, no redundancy.

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?

The tool has 10 parameters with no schema descriptions, but the description covers all parameters and usage scenarios (poll vs quiz, auto-close, etc.). The output schema exists, so return value explanation is not needed. 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?

Schema description coverage is 0%, but the description compensates fully by detailing every parameter's meaning and usage in the Args block. It adds significant value beyond the raw 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?

The description clearly states the tool creates a poll or quiz, with a specific verb '发起' (initiate). It distinguishes from siblings like vote_poll and close_poll by focusing on creation.

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 provides explicit guidance on when to use quiz mode vs regular poll, explains each parameter's role, and constraints like options count (2-10). This helps the agent decide how to configure the poll.

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