iso9000_set_phase

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

With no annotations, the description carries the full disclosure burden. It hints at a side effect (emitting a brief) and some isolation property ('role-isolated'), but says nothing about whether the transition is reversible, whether it validates the current phase, what permissions are required, or what a brief contains.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though the terseness contributes to the under-specification rather than reflecting deliberate economy.

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?

For a state-mutating tool with three parameters, zero annotation coverage, and no output schema, the description is thin. An agent cannot determine valid phase values, error behavior on invalid transitions, or the brief's format from this definition.

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 description coverage is 0%, so the description must compensate and it largely does not. It implicitly maps the three parameters (phase, role, emit_brief) to concepts, but never enumerates allowed phase values, explains the role default of 'implementer', or clarifies when emit_brief=false is appropriate.

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?

It names a specific verb ('Transition') and resource ('Agile V state machine phase') plus a side effect ('emit role-isolated subagent brief'), so the action is identifiably distinct from siblings like approve_gate1 or get_audit_chain. However, 'Agile V state machine' is unexplained jargon and the description never says what a phase actually is or which transitions are valid.

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?

There is no statement of when to call this versus the sibling tools (init_baseline, approve_gate1, verify_oracle, run_capa), no prerequisites, and no exclusions. The agent must infer the workflow position of a phase transition entirely on its own.

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