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

Beyond annotations (which only say non-read-only, open-world, non-idempotent, non-destructive), the description discloses that a public shareable page is created, that capacity is enforced so a full slot cannot be taken, and that two distinct links are returned — a public one and a private organizer one. It also notes the conditional time_zone requirement and explicitly rules out email/reminder sending and payments, all of which is behavior an agent could not infer from the structured fields.

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 short sentences, front-loaded with the use case, then the core behavior, then the return value, then scope exclusions. Nothing is repeated from the schema and 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?

For a 7-parameter creation tool with a full output schema, the description covers purpose, trigger conditions, key behavioral constraints, return shape, and out-of-scope capabilities. Return-value detail is correctly left to the output schema while the agent still learns enough to call it correctly on the first try.

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, but the description adds meaning beyond field definitions: capacity is not just a number but an enforced limit ('a full slot cannot be taken'), and time_zone becomes conditionally required when slots carry dates and times. These cross-parameter behaviors sharpen how an agent should populate 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?

The description states a concrete verb-and-resource action: it 'publishes a shared page where each person enters a first name and picks slots,' with capacity limits and two returned links. An agent can distinguish this creation tool from siblings show_signup_results (viewing) and update_signup_sheet (editing) without opening any 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?

It gives an explicit trigger, 'when the user wants people to claim slots,' plus four concrete examples (potluck dishes, volunteer shifts, carpool seats, snack turns) that make the intended context unmistakable. It also bounds scope by stating it does not send emails or reminders and does not take payments, though it never names the sibling tools as alternatives for viewing results or editing.

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