find_conflicts

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

With no annotations provided, the description carries the behavioral burden and does well by disclosing non-obvious semantics: back-to-back events are not conflicts, cancelled events are ignored, and all-day/free events are excluded unless flags are set. It does not cover read-only safety, limit/pagination behavior, or ordering, leaving some behavioral gaps.

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 tightly written and front-loads the core purpose before giving edge-case rules. Every sentence adds useful conflict-detection context, with no redundant wording or unnecessary preamble.

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 output schema exists, so return values need not be described, and the description covers key conflict-detection behavior well. However, for a 7-parameter tool with 0% schema description coverage and no annotations, important parameter semantics such as calendars and limit remain unaddressed, leaving the definition only minimally complete.

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 for parameter meaning. It explains include_all_day and include_transparent behavior and implies start/end range filtering, but it only says 'start/end/tz as in agenda,' which is not self-contained, and it leaves limit and calendars semantics unexplained.

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 states a specific verb and resource: list pairs of events whose times overlap in a range, including across calendars. This is clearly distinct from sibling tools such as agenda, search_events, and find_free_time, so an agent can identify the tool's role without opening the schema.

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 when the tool is useful by defining conflict pairs and edge cases, but it does not explicitly say when to use this tool versus alternatives like find_free_time or agenda. The inclusion and exclusion rules provide context, but there is no direct when-to-use or when-not-to-use guidance.

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