Send a poll

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

Annotations already declare this is a write/open-world operation, so the safety profile is covered. The description usefully adds that quiz requires a correct answer index and that anonymous=false reveals voters, which are behavioral traits beyond the annotations, but it omits delivery, error, or permission context for sending into a chat.

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 tight sentences with zero filler, and the core constraint (2-10 answers) is front-loaded. Every clause earns its place by clarifying a parameter behavior.

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?

For a write tool with no output schema and annotations covering the safety profile, the description supplies the key param interactions an agent needs to call it correctly. Only minor gaps remain around the chat target and error behavior.

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?

With 0% schema description coverage, the description carries the full parameter burden, and it explains the non-obvious interactions: multipleChoice allows several picks, quiz demands a 0-based correctAnswer, anonymous=false exposes voters, and answers is bounded 2-10. It leaves chat, question length, and answer max length undocumented, but nails the tricky cross-parameter semantics.

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?

States a specific verb (Send) and resource (a poll), enough for an agent to distinguish it from telegram_send_message without opening a schema. It does not name the sibling it overrides, so it stops short of a 5.

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?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives like telegram_send_message. The description explains what the poll tool accepts, not the conditions that should route an agent here.

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