calmesh_find_conflicts

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

With no annotations provided, the description carries the transparency burden. It explicitly discloses that the tool returns pairs of overlapping events and requires read scope, which gives the agent important behavioral context about safety and output shape. It doesn't cover edge cases like timezone handling or pagination, but for a simple read-only conflict finder this is sufficient.

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?

Two sentences, front-loaded with the core purpose, and every word earns its place. It states the action, the output, and the access requirement without any filler.

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?

Given the simple nature of the tool and no output schema, the description adequately explains what is returned ('pairs of events that overlap') and the required access level ('read' scope). It doesn't address potential edge cases, but the tool is straightforward and the description is sufficient for an agent to select and invoke it correctly.

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 input schema already fully describes all three parameters (slug, start, end) with 100% coverage, so the description doesn't need to add much. The phrase 'within a date range' aligns with start/end but doesn't add new meaning beyond the schema. Baseline 3 is appropriate.

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 uses a specific verb ('Find') and identifies the exact resource ('overlapping events/conflicts') plus the scope ('within a date range'). It clearly distinguishes this from siblings like get_events or check_availability by focusing on conflict detection and explicitly stating it returns overlapping pairs.

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?

Provides clear context: use it to find overlapping events in a date range, and notes that it requires 'read' scope. It doesn't explicitly name alternatives or exclusions, but the stated scope and behavior make the appropriate use case obvious.

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