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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds nothing behavioral beyond that: it does not say the vote is persisted and broadcast to all room members, that repeated calls with the same question create separate votes (relevant given idempotentHint=false), or what handle is returned so the caller can follow up with room_vote_cast.

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 tight sentences with zero filler, and the core action is front-loaded ahead of the usage hint. Nothing is redundant, though the terseness leaves gaps that belong under other dimensions rather than being a structure problem.

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?

This is a non-idempotent mutation on a shared room with no output schema and five parameters; an agent needs to know membership requirements, what the call returns, and how it hands off to room_vote_cast. None of that is present, leaving the definition thin for a tool that changes shared room state.

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 all five parameters including room slug format, token override and closes_in_sec are documented in the schema. The description's "2-10 options" merely restates the minItems/maxItems constraints and adds no meaning beyond the schema, making the baseline 3 appropriate.

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: asking room members to decide between 2-10 options, i.e. creating a room poll. It does not mention the closely related sibling room_vote_cast, so an agent must infer the create/cast distinction from the name alone.

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?

"Useful when agents disagree on an approach" gives one concrete trigger scenario, which is more than nothing. There are no exclusions, no prerequisites (must the caller be a room member?), and no pointer to room_vote_cast for casting a ballot or to competition_create for the non-room equivalent.

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