search_slots

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

With no annotations, the description discloses that the tool is 'Read-only', that booking_string is single-use and can expire, that end_date is ignored server-side (dropped client-side), and that next_search_date hints pagination. This provides sufficient behavioral insight beyond the schema.

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 a single, well-structured paragraph with no redundant sentences. It front-loads the core purpose and follows with necessary details. Every sentence adds value and 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?

Given the complexity (9 parameters, output schema exists), the description covers key aspects: main function, optional filters, pagination hint, expiration, and client-side filtering limitations. It does not explain output schema details (which is acceptable) or error handling, but is complete enough for typical use.

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%, but the description adds value beyond schema descriptions: it explains the purpose of booking_string (carried in each slot), the need for client-side filtering of visit_type, and the expiration hint. This additional context helps the agent understand how to use parameters effectively.

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 verb 'Find' and the resource 'available appointment slots', with optional filters. It distinguishes from siblings like book_appointment (which uses the booking_string) and list_appointments (which lists existing appointments). The explanation of booking_string and visit_type further clarifies the tool's role.

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 usage guidance: 'Re-run this immediately before booking, because a booking_string can expire.' It also advises on filtering visit_type client-side for in-person visits. Although it does not explicitly state when not to use it, the context implies it for finding slots before booking. Alternatives like list_search_filters are mentioned for resolving language IDs.

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