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

No annotations provided, so description carries full burden. It discloses a key behavioral trait: slot times are returned in the venue's timezone, not necessarily the directory's. Also implies dependency on consistent place_slug. However, it doesn't describe response format or error behavior, but the timezone warning is valuable.

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?

Three sentences, front-loaded with purpose, then usage instructions, then the timezone caveat. Every sentence contributes essential information without redundancy or unnecessary fluff.

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 3-parameter tool with no output schema, the description covers input semantics and a critical timezone behavior. It doesn't describe the response structure (e.g., array of slots) or error cases, but given the tool's simplicity and the presence of sibling list_booking_services, the description is largely adequate.

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 baseline is 3. The description adds meaning beyond the schema by specifying the provenance of serviceId (from list_booking_services) and the need to pass the same place_slug. This enriches parameter understanding and cross-tool consistency.

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 specific verb ('Get') and resource ('available time slots for a bookable service'), with the scope (given date via Wix Bookings). It distinguishes itself from siblings like create_booking by focusing on availability retrieval.

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 clear context on when to use: pass serviceId from list_booking_services, date in YYYY-MM-DD, and same place_slug used there. The timezone caveat adds practical guidance. It doesn't explicitly state when not to use alternatives, but the cross-tool references make usage clear.

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