get_free_slots

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

No annotations are present, so the description must disclose behavior. It adds a useful detail: 'Handles the epoch-milliseconds requirement for you,' but it does not mention whether the operation is read-only, what side effects exist, error behavior, or return format. Some context is provided, but significant gaps remain.

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-loaded with the core purpose, and contains no redundant or extraneous information. Every word 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?

There is no output schema, so the description must explain what the returned slots look like—especially since book_appointment likely needs a slot identifier. It does not describe the return structure, nor does it address how timezone affects slot availability. This makes it insufficient for an agent to fully chain with the sibling tools.

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 75% (three of four parameters have descriptions). The description adds value by revealing that date parameters are automatically converted from ISO 8601 to epoch milliseconds, which is not stated in the schema. It does not clarify calendarId or timezone semantics further, but the added detail improves parameter understanding.

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 tool gets 'real bookable slots' for a specified calendar and date range, using a specific verb and resource. This distinguishes it from siblings like book_appointment and list_calendars.

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 implies usage for finding available slots before booking, but it does not explicitly say when to use this versus alternatives, nor does it mention any exclusions or prerequisites. The guidance is only implicit.

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