check_conflicts

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

With no annotations, the description carries the full burden and does well: it discloses the end-defaulting rule (start + 1 hour), the whole-day input format, the calendar scope behavior, and the shape of the return (events each with their calendar, all_day flag). It stops short of stating permissions or whether the check is purely read-only, but the operational behavior is well 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?

Three short sentences, front-loaded with the core question then the input formats then the output. The rhetorical opening 'What overlaps a proposed time?' is slightly stylized but still earns its place as a purpose statement.

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?

For a 3-parameter read tool with no output schema and no annotations, the description covers purpose, input formats, defaults, scope, and return shape — enough for an agent to call it correctly. Missing only secondary details such as timezone semantics and result ordering.

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 0%, so the description must compensate — and it does, documenting start, end (including its default), and calendars ('or the named ones'). Only timezone handling for the ISO datetimes is left ambiguous.

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?

States a specific operation (find what overlaps a proposed time interval) on a clear resource (calendar events), which an agent can readily separate from list_events or search_events. It never names a sibling to differentiate against, but the conflict-detection framing is distinctive enough on its own.

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 phrase 'a proposed time' implies the pre-creation check use case, but there is no explicit when-to-use or when-not-to-use guidance and no routing to close siblings like find_free_time or propose_event. Usage is inferred rather than stated.

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