check_attendee_availability

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

No annotations provided, so description carries full burden. It discloses automatic inclusion of organizer, automatic time range calculation based on working hours, and support limit of 20 attendees. Return format and availability codes are explained. Lacks details on authentication or side effects, but adequate for a read-like tool.

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?

Description is concise: 5-6 well-organized sentences. First sentence states purpose, then workflow, automatic behaviors, return format with codes, and a final note on limits. Every sentence adds value with no redundancy.

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?

Despite no output schema, description details return fields including availability view codes. Covers all 7 parameters and key behaviors. For a 2-required-param tool with good description, it is complete enough for an agent to use 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 100% (all 7 parameters described). Description adds meaning beyond schema: 'time range will be automatically calculated' for date, 'Used to find continuous free time slots' for meeting_duration, and explains top_slots and availability_view_interval purpose.

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?

Description starts with a clear verb+resource: 'Check availability of attendees for a given date.' It distinguishes from siblings by specifying the workflow: 'Typically use before calling manage_my_event with create action to find optimal meeting times.'

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?

Provides explicit context: 'Typically use before calling manage_my_event with create action to find optimal meeting times.' It also notes automatic behaviors (includes organizer, auto-calculates time range). No explicit alternatives or when-not-to-use, but clear enough.

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