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

With no annotations provided, the description carries full behavioral transparency burden. It discloses an important behavioral trait: slot times are returned in the VENUE's timezone, not necessarily the directory's. It implies read-only behavior. However, it does not mention return format, error cases, or authentication needs.

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?

The description is three sentences with no wasted verbiage. The first sentence states the purpose, the second provides instructions, and the third gives a critical behavioral note. It is front-loaded and efficiently conveys all necessary information.

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?

Given the absence of an output schema, the description adequately covers parameter usage but does not describe the format of the returned time slots. While the tool's function is clear, an agent might need to know whether slots are returned as strings or objects. The completeness is adequate but not full.

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 baseline is 3. The description adds value beyond schema by explaining why the same place_slug must be used and adds the timezone context that affects parameter interpretation. The schema already includes parameter descriptions, but the tool description enhances understanding.

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 clearly states the tool retrieves available time slots for a bookable service on a given date (Wix Bookings). It distinguishes from sibling tools like create_booking (which creates) and list_booking_services (which lists services) by specifying that the serviceId comes from list_booking_services.

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?

The description gives explicit instructions on when to use the tool: to get available time slots for a specific date. It provides step-by-step guidance on parameters (serviceId from list_booking_services, date format, same place_slug). It does not include explicit exclusions or alternatives, but the context is clear.

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