check_availability

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

With no annotations provided, the description fully discloses key behaviors: past slots are excluded automatically, return includes 'next_available' for alternatives, and time zone is clinic-local. This goes beyond the schema and gives the agent confidence in side-effect-free checking.

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?

Every sentence earns its place—summary, usage rule, behavior note, parameter details, and example. It is compact yet comprehensive, with clear front-loading of purpose and no redundant phrasing.

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 description covers standard usage (pre-booking), edge cases (no open slots), and all parameters with defaults. It even explains the 'next_available' field, supplementing the output schema. The tool is fully contextualized within the booking workflow.

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 Args section compensates for the 0% schema description coverage by explaining each parameter: doctor_id sourced from list_doctors, date format and default, and how days_ahead scans. The example call ties it together, making parameter usage unambiguous.

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 opens with a specific verb and resource: 'Find open appointment slots for a doctor, in clinic-local time.' It clearly differentiates from sibling tools by explicitly positioning itself as a pre-booking check ('Always call this before book_appointment').

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?

It provides explicit when-to-use guidance ('Always call this before book_appointment') and practical context for the 'days_ahead' parameter ('Use 7 for "sometime next week"'). It also explains the fallback behavior via 'next_available' for handling empty availability.

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