loop_advance

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

No annotations are provided, so the description should fully disclose behavior. It only lists triggers and their resulting phases, but does not mention side effects, permissions, idempotency, or error conditions. The state transition is implied but not explicitly confirmed as a mutation.

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 extremely concise: two sentences and a structured list. Every element is necessary and front-loaded. No redundancy or filler.

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?

With an existing output schema, return values are covered. However, the description lacks behavioral details (e.g., prerequisites, failure modes) that would help the agent use it confidently. It is moderately complete for a simple tool but has gaps.

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% but only provides basic descriptions. The description adds critical meaning by listing available triggers and mapping each to the next phase, which is essential for correct invocation. Without this, the agent would not know valid trigger 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 action 'Advance the loop to the next phase' and specifies the resource ('loop'). The list of triggers distinguishes it from similar tools like pipeline_advance and other loop tools.

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 implicitly defines when to use the tool via trigger list, but lacks explicit guidance on when not to use it or alternatives (e.g., for checking loop status use loop_status). No comparisons to siblings.

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