delimit_sense

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

With no annotations, the description fully discloses behavioral traits: side effects for each action (e.g., 'promote' writes a new ledger item, 'freeze' cold-archives) and the storage location (~/.delimit/intel/signals/). Read-only and write actions are clearly separated.

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 concise and well-structured with clear sections: when to use, not to use, sibling contrast, and side effects. It is front-loaded with the main purpose and avoids unnecessary detail.

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 presence of an output schema (noted in context signals), the description need not explain return values. It covers all essential aspects: purpose, usage, side effects, and sibling distinction, making it complete for an agent.

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 100%, so the baseline is 3. The description adds context for the 'action' parameter by explaining each action's effect, but other parameters are already well-documented in the schema. No significant additional meaning beyond schema.

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 clearly states the tool's purpose: 'Review and manage the signal corpus (LED-877).' It specifies actions like inspect, cluster, and promote, and distinguishes from sibling tools like delimit_reddit_scan and delimit_github_scan.

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?

Explicitly provides 'When to use' and 'When NOT to use' sections, detailing appropriate use cases (inspect, cluster, promote) and exclusions (fetch new signals, write ledger items directly). Also includes sibling contrast for additional guidance.

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