delimit_collision_check

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

Discloses side effects: claim/release mutate lock state, check is read-only. No annotations provided, so description fully handles behavioral disclosure with no contradictions.

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?

Concise three-section structure (purpose, usage, side effects) with no wasted words. Front-loaded with core purpose. Every sentence adds value.

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 moderate complexity (4 params, no annotations, output schema exists), description covers purpose, usage, side effects, and sibling contrast. Output format not needed due to output schema.

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 100%, so description adds little beyond what schema already provides. Description repeats schema text for file_path but does not significantly enhance parameter meaning.

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?

Clearly states the tool detects/prevents multi-model file edit collisions, with specific verb and resource. Explicitly differentiates from sibling delimit_swarm by stating it tracks per-file edit ownership.

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 explicit 'When to use' (cross-model workflows, claim before edit, release after commit) and 'When NOT to use' (single-model sessions, general filesystem locking). Clear guidance on context.

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