agloop_set_phase

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

No annotations are provided. The description does not disclose any behavioral traits such as side effects, idempotence, consequences of transitioning, or what happens to ongoing processes. The single phrase 'Transition to a new phase' gives no behavioral insight beyond the action itself.

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 short (5 words), which can be seen as concise, but it severely under-specifies the tool. Important information is missing, making it not truly concise but rather inadequate. Every sentence should earn its place, but here even the single sentence is insufficient.

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 has one required parameter, no schema descriptions, and an output schema that is not explained, the description is incomplete. It fails to explain what phases are, the effect of transitioning, or any return value. For a state-changing tool, more context is needed for correct invocation.

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 0% - the description does not explain the 'phase' parameter at all. It only says 'Transition to a new phase', but does not specify valid values or format. Since there are no enums, the description should clarify acceptable phase 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?

Description states 'Transition to a new phase' which indicates the tool changes the phase state. However, it lacks specificity about what a phase is and doesn't distinguish from any sibling tools. The name 'set_phase' provides some clarity but the description barely expands.

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?

Only usage guidance is 'COORDINATOR ONLY', implying role restriction. No context on when to transition phases, prerequisites, or alternatives. No mention of when not to use this tool.

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