slots_list

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

No annotations provided, so the description must fully disclose behavior. It lists the operation as read-only (listing) but does not mention what happens if both identification methods are provided, timezone handling, pagination, or any side effects. Minimal disclosure.

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 two sentences, front-loading the core action. No unnecessary words. However, it could be slightly expanded to include missing details without becoming verbose.

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 6 parameters, no output schema, and no annotations, the description is incomplete. It omits return value format, parameter formats, and handling of edge cases (e.g., no available slots). Does not fully equip an agent to use the tool correctly.

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 0%, so the description must compensate. It clarifies the mutual exclusivity between eventTypeId and (username+eventTypeSlug), which is not in the schema. However, it does not explain the format of startTime/endTime, the role of duration, or other constraints. Partial addition of meaning.

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 uses a specific verb ('List') and resource ('available booking slots') and clearly states the scope ('in a time range'). It also specifies the identification parameters, distinguishing it from sibling tools like bookings_list or event_types_list.

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?

The description mentions the required identification parameters but does not provide guidance on when to use this tool versus alternatives (e.g., when to use slot search vs. booking list). No when-not or comparison to siblings.

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