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

No annotations provided, so description carries full burden. Discloses time zone behavior but does not explicitly state that the tool is read-only or idempotent. Adequate but could be more transparent.

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?

Very concise (2 sentences) with no unnecessary words. Information is front-loaded: the tool's purpose and key parameters are immediately clear.

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 no output schema, description does not explain what the response looks like (e.g., list of time slots, any pagination). Lacks details on returned data format, which would help an agent use the result.

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?

Adds significant meaning beyond the schema: explains that serviceId comes from list_booking_services, date must be YYYY-MM-DD, and place_slug must match the one used in list_booking_services. Also adds context about time zones for the slot times.

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's purpose: 'Get available time slots for a bookable service on a given date (Wix Bookings).' It uses a specific verb and resource, distinguishing it from sibling tools like create_booking.

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: pass serviceId from list_booking_services, date format YYYY-MM-DD, and same place_slug. Also warns about time zone differences. Does not state when not to use or mention alternatives like create_booking.

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