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

Annotations only say it's a non-read-only, open-world, non-idempotent write. The description adds what the agent actually needs: a public live page with a share link, a separate private organizer link, waitlists for full slots, day-before reminders, and that money is pledged and paid directly to the organizer rather than held by the service.

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 purpose, then use-case recognition, then exclusions — a sensible order with no filler sentences. The middle use-case list is long (potluck, class party, volunteer shifts, carpool days, meal train, conference slots, supplies, classroom helpers), which aids recognition but reads as a run-on list that could be tightened.

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 an 11-parameter nested creation tool with an output schema, the description covers what gets created, what is returned (share link and organizer link), and the key downstream behaviors. Return-value detail is rightly left to the output schema and parameter detail to the fully described schema.

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 coverage is 100%, so the baseline is 3. The description goes further by explaining the slot model — label, optional date and start/end time, capacity — and the behavioral consequence of capacity ('full slots get a waitlist and people get a reminder the day before'). It says nothing about the chip_in money-collection object, leaving that entirely to the 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?

Opens with a specific verb and resource ('Creates a live online sign-up sheet on SignUpSheet.page') and states the core mechanism: one shared link, no account needed. It explicitly rules out sibling use cases ('Not for voting on dates, group cards...'), which maps directly to create_date_poll and create_group_card.

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 a concrete when-to-use list (potlucks, volunteer shifts, meal trains, conference slots) and an explicit when-not-to-use list (voting on dates, group cards, ticket sales, paid registration). The boundary against the two sibling creation tools is stated, not implied.

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