calendar_findFreeTime

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

The annotation readOnlyHint=true already indicates this is a safe read operation. The description adds the context of 'multiple people' but does not disclose additional behavioral details such as how availability is determined or what happens if no slot exists. This matches the baseline for a read-only tool with minimal description.

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 phrase that is concise and front-loaded. It contains no filler or redundant information.

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?

The tool has no output schema, and the description does not specify the return format (e.g., a specific time slot object). However, the required parameters are fully documented and the read-only annotation covers safety. The description is sufficient for basic invocation but lacks some context about behavior and output.

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 provides 100% coverage with descriptions for all four parameters (attendees, timeMin, timeMax, duration). The tool description adds no additional parameter-level semantics beyond what the schema already states, so a baseline score of 3 is appropriate.

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's function: finding a free time slot for multiple people. This distinguishes it from sibling tools like calendar_listEvents (which lists events) and calendar_createEvent (which creates events).

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 this tool is used when you need to find a mutual free time among multiple attendees, but it does not explicitly state when to use it over alternatives or exclude other scenarios. There is no mention of specific conditions like checking calendars or creating events afterward.

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