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

Annotations already declare the safety profile (not read-only, not destructive, closed world), so the bar is lower. The description still adds real behavioral context beyond them: the call produces a shareable link and voters need no account. It does not discuss auth requirements for creating, editability, or closure defaults beyond what the schema says.

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?

Two front-loaded sentences with no filler; the key benefit (share link) and the audience fact (no account to vote) both earn their place. It is slightly short of ideal for a seven-parameter tool with five voting styles, but nothing is wasted.

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?

With full schema coverage, no output schema, and safety annotations present, the description covers the essentials and usefully states the primary return value (a share link). It leaves minor gaps around the creation-side auth/privacy expectations and what happens after creation, but an agent can call it correctly as-is.

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 100%, so the schema already carries all parameter meaning, including votingStyle, optionKind, and the per-option shape. The description contributes nothing parameter-specific, which is the correct baseline-3 outcome when the schema does the heavy lifting.

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 gives a specific verb and resource ('Create a Pickly poll') plus the concrete outcome ('get a link to share in the group chat'), with example use cases (where to eat, which date, what to watch). It does not explicitly name or contrast with the sibling get_results, but the create-vs-retrieve verbs make the split obvious.

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?

It clearly frames when to reach for this tool: group decisions with multiple participants, and it implies the follow-on step of sharing a link. There are no exclusions or explicit alternatives named (e.g. what to do if a poll already exists), so it falls short of a 5.

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