delimit_self_repair_daemon

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

No annotations provided, but the description fully discloses side effects: mutation on start/stop, idempotent start, circuit-breaker stop after 3 consecutive failures, environment variable handling (DELIMIT_SELF_REPAIR_PAUSE=1), and chaining of higher modes when configured.

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?

Well-structured with sections, but slightly verbose with internal reference (LED-191) and minor redundancy. Each sentence adds value, but could be trimmed for brevity.

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 complexity of daemon control with multiple actions and side effects, the description covers all essential aspects. Output schema exists (per context signals), so return values are handled. No gaps identified.

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% (only 1 parameter), but the description adds context beyond the schema's action description by explaining idempotency, circuit-breaker, and env var behavior. However, the schema already provides a good description of action values.

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 controls the self-repair watcher daemon, with specific verb 'Control' and resource. It distinguishes from siblings by naming delimit_daemon_status, delimit_inbox_daemon, and delimit_social_daemon.

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?

Explicit 'When to use' and 'When NOT to use' sections with direct tool name mentions for alternatives. Also provides sibling contrast explaining the difference from delimit_daemon_status.

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