find_next_available

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

Annotations already indicate readOnlyHint and idempotentHint. The description adds the null return behavior but omits crucial information about location-based filtering (latitude, longitude, radius_km), which are part of the parameters and affect the search. This is a notable gap.

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, well-structured sentence that frontloads the core behavior. Every word is informative; no fluff or repetition.

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 having an output schema, the description fails to mention the location parameters that significantly affect the tool's behavior. For a tool with 7 parameters and location filtering, this omission leaves the description incomplete.

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 description coverage is 57%, with latitude, longitude, and radius_km lacking descriptions. The tool description does not compensate by explaining these parameters or their role (location proximity). It only implicitly covers date, days, and time. Thus, it adds little value beyond the schema.

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 precisely states the tool finds the first day within a window that has a free, qualified staff member at a given time, including the null case. It clearly distinguishes from sibling tools like search_availability by specifying 'first' and 'within days'.

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 the earliest available date matching criteria, but it does not explicitly state when to use this tool over alternatives (e.g., search_availability for broader searches). No exclusion criteria or context are provided.

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