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

Adds substantial context beyond the annotations: it is a write that 'sends no emails and touches no calendars', it returns a vote link, and non-Lucie participants can vote manually. It also discloses the Sync Pro/Membership gating, which the annotations (openWorldHint only) cannot convey. This is exactly the behavioral detail a caller needs before creating the poll.

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?

Front-loaded with the core action and outcome, then prerequisites; every sentence carries information. It is dense and slightly long for one paragraph, but no sentence is filler.

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 8 parameters, no output schema, and a mutation of medium complexity, the description covers what the tool creates, what it returns (a vote link), side effects (no emails/calendar writes), and the licensing prerequisite. Nothing essential for correct invocation is missing.

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 documents all 8 parameters (handles, from/to window, timeZone, durationMinutes, organizer fields). The description explains the semantics of the seeded candidate times (intersection of availability) and confirms duration with the organizer, but adds no per-parameter format or constraint detail beyond the schema. Baseline 3 applies.

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 and resource ('Create a Lucie group event (a poll)') and immediately clarifies the resource is a scheduling poll seeded with the intersection of participants' availability, which separates it from the read-only find_group_times and the booking-oriented book_group_meeting. An agent can tell what it produces (a poll + vote link) without opening the schema.

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?

Gives clear context and prerequisites: confirm title/participants/duration with the organizer first, and the organizer must be on Sync Pro or hold a Lucie Membership. It does not explicitly name sibling alternatives ('use find_group_times first, then book_group_meeting when a time is chosen'), so routing is implied rather than stated.

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