delimit_build_loop

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

The description discloses some behavioral traits (auto-triggering stages, failed stages not blocking subsequent ones) but lacks detail on side effects, auth requirements, or failure modes. With no annotations, it partially fulfills the transparency burden.

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, uses bullet points for clarity, and front-loads the main purpose. It is well-structured without unnecessary details.

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 (4 parameters, output schema), the description covers the core functionality but omits guidance on session handling or detailed use cases for each loop type. It is minimally complete.

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 has 100% coverage, so the description's additional explanation of loop_type adds value but is not critical. It does not elaborate on action, session_id, or cycle_mode 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 articulates the tool's purpose: executing a governed continuous loop (LED-239) with four specific loop types. It distinguishes the tool from siblings by focusing on loop execution, but does not explicitly differentiate from closely related tools like delimit_build_loop_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?

While it lists loop types and recommends 'cycle', it provides no explicit guidance on when to use this tool vs alternatives (e.g., when to choose build over social), nor does it mention prerequisites or exclusions.

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