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

Annotations already establish the non-read-only, non-destructive, open-world profile; the description adds real context beyond that: it requires a Cotlet API key, it reaches other people so confirmation is advised, and the date field drives when Vagaro notifies the client. It does not describe failure behavior or the exact confirmation mechanism, keeping it just below the top.

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, which is good, but the confirmation instruction is redundant across two sentences ('By default you confirm each call' and 'confirm with the user before each call'), and the opening restates the same operation twice ('put a client on the waitlist' / 'adds a client to the waitlist'). Some trimming is warranted.

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 5-param mutation with no output schema, it covers the essential points: side effect (reaches other people), auth requirement, confirmation behavior, and return value (entry ID for list_waitlist). Nothing critical is missing, though the alternative-routing context is thin.

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 already 100%, so the baseline is 3, but the description adds meaning by explaining that date 'tells Vagaro when to notify the client' (beyond the schema's terse 'Day the client wants') and clarifies provider is a preferred/default choice. Genuine additive value over 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?

States a specific verb and resource ('put a client on the waitlist for a service, provider and day') plus scope, and links to siblings by naming list_waitlist as the consumer of the returned entry ID. An agent can distinguish this from vagaro_list_waitlist and vagaro_notify_waitlist 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?

Provides confirmation guidance ('by default you confirm each call; you can switch that off') and a safety condition ('confirm with the user before each call'), but never states when to prefer this over booking or search_availability. Usage context is implied rather than spelled out against alternatives.

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