Delimit Ledger Auto Cancel Stale

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

Beyond the destructiveHint annotation, the description discloses the key side effects: with dry_run=False it archives via bulk_action(archive), with dry_run=True it returns only the plan, items are never hard-deleted, and the JSONL append-only log retains full records. It also explains the composition with the stale-detector and bulk_action, which goes well beyond what annotations alone provide.

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 well-organized with clear sections and front-loaded purpose, but it is somewhat long and repeats sibling contrast in both the 'When NOT to use' and 'Sibling contrast' sections. The trailing internal reference 'LED-1145 Phase 2 #4' also adds little value for an agent selecting or invoking the tool.

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 tool's complexity, destructive nature, and rich sibling set, the description covers selection criteria, invocation semantics, dry-run behavior, persistence guarantees, and composition with bulk actions. An output schema exists, so lack of explicit return-value detail is acceptable; nothing essential for correct use is missing.

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 covers all four parameters with detailed descriptions (100% coverage), so the baseline is 3. The tool description adds general context about the 60-day default and strict threshold, but does not materially extend the schema's parameter-level explanations.

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 action (auto-archive open ledger items dormant past stale-TTL threshold) with the resource and behavior clearly named. It differentiates itself from siblings like delimit_ledger_groom and delimit_ledger_auto_close_external, so an agent can select it accurately.

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 gives explicit 'When to use' and 'When NOT to use' guidance, naming exact alternatives (delimit_ledger_groom, delimit_ledger_health, delimit_ledger_auto_close_external) and the conditions that route to each. This is ideal for an agent deciding between closely-related ledger tools.

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