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

Discloses that slot times are returned in the venue's timezone, not the directory's. No annotations provided, so description carries full burden; could mention error handling or output format, but the key behavioral trait is covered.

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 with no unnecessary words. Critical info is front-loaded. Each sentence adds value.

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 could have described the response format (e.g., array of slots). However, inputs are well-covered, and the timezone note is helpful. Lacks info on error cases or empty results.

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%, and the description adds value by specifying provenance of serviceId, consistent place_slug, date format, and timezone insight, all beyond the schema's brief descriptions.

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 the tool gets available time slots for a bookable service, distinguishing it from siblings like list_booking_services (which lists services) and create_booking (which creates bookings).

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?

Specifies passing serviceId from list_booking_services, date in YYYY-MM-DD, and same place_slug. Highlights timezone caveat. No explicit when-not-to-use, but context is clear.

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