Find available slots

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior. The description adds useful behavioral context: 'Times are wall clock in the business's time zone; closed days have no times' and sequential service scheduling. No contradictions with annotations.

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, front-loaded with purpose. The second sentence is slightly redundant with 'Asks the calendar for free start times as New appointment does,' but overall the description is efficient and every sentence contributes.

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 exists, but the description conveys return structure ('day by day') and key behavioral traits (timezone, closed days). For a read-only tool with full annotations and complete parameter schema, this is sufficiently complete.

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 the baseline is 3. The description reiterates 'one or more services' and 'up to 14 days' but adds little meaning beyond what the schema already provides (e.g., service_ids order, days min/max/default are all documented in the schema).

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: 'Free start times for one or more services with a team member, day by day.' It also distinguishes from the booking tool by directing the agent to create_appointment. An agent can readily tell what this tool does versus siblings.

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 a clear next step: 'Book a time with create_appointment.' However, it does not explicitly state when NOT to use this tool or contrast it with other listing tools like list_appointments. Implied usage is clear enough for an agent to select it before booking.

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