getBookableItems

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only operation by using 'Get', but it does not describe any behavioral traits such as how availability is determined, whether results are paginated, or any authentication requirements. The description is minimal and adds little beyond the tool name.

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 short sentence, which is concise and front-loaded. However, for a tool with six parameters and no output schema, the brevity comes at the expense of essential information, making it under-specified. It is not verbose, but it is not adequately informative either.

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 tool's complexity (6 parameters, no output schema, no annotations), the description is incomplete. It fails to explain how parameters like startDate/endDate, staffIds, locationIds, and appointmentId affect the results, what the return value looks like, or any limitations. This leaves the agent with insufficient guidance for correct invocation.

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?

The input schema has 100% description coverage, with each parameter given a basic label (e.g., 'Start date', 'Staff IDs'). The tool description adds no additional meaning beyond 'available appointment slots', which implicitly connects the parameters to filtering availability but does not explain parameter interplay or formatting. This meets the baseline for high schema coverage but does not exceed it.

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 'Get' and a clear resource 'available appointment slots', which accurately conveys the tool's purpose of retrieving bookable slots. However, it does not differentiate from sibling tools like getActiveSessionTimes or getScheduleItems, which also retrieve time-related information, so it is clear but not fully distinguished.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any exclusions, prerequisites, or mention sibling tools, leaving the agent without context for tool selection in a list of many appointment/schedule-related tools.

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