delimit_sense

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

The description discloses that the tool can manage signals (implied mutations via promote and freeze), but without annotations, it fails to specify read/write behavior, destructiveness, or permissions. It partially covers behavioral traits but lacks thoroughness.

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 sentences efficiently cover purpose, location, and usage without redundancy. Key information is front-loaded.

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 an 8-parameter tool with output schema, the description adequately explains the tool's role and main actions. It could elaborate on specific actions like 'freeze', but overall is sufficient for agent understanding.

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% with parameter descriptions, so baseline is 3. The description adds context about signal location and promotion but does not enhance individual parameter meaning beyond the 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: to review and manage the signal corpus. It specifies actions like inspect, cluster, and promote signals to ledger items, and distinguishes itself by mentioning physical separation from the ledger.

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 to use the tool (for signal corpus operations) but does not explicitly exclude scenarios or name alternative tools. The mention of promotion to ledger hints at the boundary between signal and ledger tools.

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