Find available times

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

Discloses a genuinely non-obvious side effect beyond the annotations: despite the 'find' name, it starts a booking intent and returns an intentId. This is exactly the kind of hidden state creation an agent needs, and it aligns with (rather than repeats) readOnlyHint=false.

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 zero filler; the purpose and return grouping come first, then the handoff to book_time. Every clause earns its place.

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?

With no output schema, the description covers the key return value (intentId) and result grouping, and all parameters are schema-documented. Minor gaps remain: no mention of behavior when no slots are available, intent expiry, or pagination limits.

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 the schema already documents all seven parameters, including examples for from/until and the IANA timeZone. The description adds only the downstream intentId/startsAt pairing, so baseline 3 is appropriate.

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?

States a specific verb and resource ('Find open times on a booking page') plus the return shape ('grouped by day with readable local times'). This clearly distinguishes it from sibling reads like get_booking_page and from the downstream book_time action.

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?

Explicitly frames the tool as the first step of a booking flow and routes the agent to book_time with the intentId and an exact startsAt. It gives a clear use context but does not state when NOT to use it or how it relates to reschedule/cancel flows.

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