find_free_time

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

With no annotations, the description bears full responsibility for disclosing behavior. It specifies that the tool only examines the user's own calendar and only returns slots within working hours (default 9-18). It does not mention potential limitations like ignoring holidays or overlapping events, but it provides adequate transparency for typical use.

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 well-structured with a one-line summary followed by clearly formatted Args and Returns sections. Every sentence is informative, no wasted text, and the most important information (purpose) is front-loaded.

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 has 5 parameters, no annotations, and an output schema, the description is nearly complete. It covers all parameters, default behaviors, and return format. It could mention timezone handling or what happens when no free time exists, but overall it is sufficient for correct tool selection and 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 schema has 0% description coverage, so the description adds complete parameter semantics. It explains each parameter (start_date in YYYY-MM-DD, end_date defaults to start_date, duration_minutes default 30, start_hour default 9, end_hour default 18), which adds significant meaning beyond the schema's titles.

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 finds free time slots in the user's own calendar, which is a specific verb-resource combination. It distinguishes itself from siblings like 'find_meeting_time' by focusing on the user's personal calendar rather than group scheduling.

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 it is for analyzing one's own calendar to find available slots within working hours, but it does not explicitly state when to use this tool versus alternatives (e.g., 'find_meeting_time' for group availability). The context is clear but no exclusions or alternative guidance is provided.

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