Find availability conflicts

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

Annotations already indicate read-only and idempotent behavior. The description adds only that the tool finds overlapping rosters, which is already clear from the name. No additional behavioral traits like return format or performance implications are disclosed.

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?

A single, concise sentence that is front-loaded with the core purpose. No extraneous 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 description does not explain the return value or output format. Given no output schema, this is a significant gap. The tool has 4 parameters and no output schema, so the description should clarify what the result looks like.

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 75% (three of four parameters have schema descriptions). The tool description does not add meaning for parameters beyond the schema. Baseline of 3 is appropriate as schema does most of the work, but location_ids lacks schema description and tool description does not compensate.

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 clearly states the tool finds rosters overlapping recorded unavailability or approved leave. The verb 'Find' and resources are specific. It distinguishes from siblings like find_coverage_gaps (coverage gaps) and flag_overtime_risk (overtime risks).

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 detecting conflicts between rosters and unavailability/leave, but does not explicitly state when to use this tool versus alternatives. No when-not or exclusion criteria are provided.

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