delimit_build_loop

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

No annotations provided, so the description carries the full burden. It details side effects for each loop_type (e.g., cycle dispatches swarm work, social drafts replies, deploy runs gates) and mentions writing to the session record. However, it does not discuss idempotency, error behavior, or permission requirements, which would elevate it to a 5.

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-structured with clear headings for usage, side effects, and loop types. It is concise—every sentence adds value—and front-loaded with the tool's core purpose.

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 (4 parameters, no annotations, output schema exists), the description is thorough. It covers when to use, side effects, and loop type details. The output schema likely explains return values, so the description does not need to repeat that.

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 baseline is 3. The description adds value by explaining the semantics of loop_type and cycle_mode beyond the schema's simple type descriptions, such as what each loop type does and the cycle_mode options. This complements the schema well.

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 'execute[s] one iteration of a governed continuous loop'. It specifies the verb 'execute', the resource 'governed continuous loop', and distinguishes from siblings like delimit_loop_status and delimit_loop_config. The inclusion of loop types adds further clarity.

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 ('advance the autonomous build / social / deploy loop one step') and when NOT to use (for status use delimit_loop_status, for configuration use delimit_loop_config). Also contrasts with sibling tools, offering clear guidance.

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