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

No annotations present, so description carries full burden. It discloses that slot times are in the venue's timezone, not necessarily the directory's. It implies a read-only operation. Could add more on error handling or output format, but sufficient for typical use.

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?

Two sentences, no wasted words. First sentence introduces purpose and context, second covers a key behavioral detail. Front-loaded and efficient.

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?

No output schema, so description should cover return format but does not. However, for a 3-parameter tool with no enums and simple input, the description is reasonably complete. Could be improved by mentioning what the output contains (e.g., time slots).

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%, but description adds context: serviceId sourced from list_booking_services, date format confirmed, place_slug must match, and critical timezone nuance not in schema. Adds significant value beyond parameter names and types.

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?

Clearly states it gets available time slots for a bookable service on a given date, with specific reference to Wix Bookings. The verb and resource are precise, and it is distinguishable from sibling tools like create_booking or request_reservation.

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 explicit guidance on how to use the tool: pass serviceId from list_booking_services, date in YYYY-MM-DD, and the same place_slug. It also warns about timezone behavior. Does not explicitly state when not to use, but context is strong enough.

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