Run synthetic G2 fixture baseline through snapshot, sheet, HITL, and audit-gate checks to validate pipeline acceptance.
Run the synthetic G2 fixture baseline through snapshot, sheet, HITL, and audit-gate acceptance.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must fully disclose behavior. It mentions running through multiple steps but does not specify side effects, whether it is read-only or destructive, error handling, or what happens to data.
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 a single sentence, concise and front-loaded with the key action. It efficiently conveys the pipeline steps without waste.
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?
Despite having no parameters, the tool runs a complex pipeline and lacks context on implicit inputs, acceptance criteria, or output format. The description is too brief for an agent to fully understand the tool's role.
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?
There are zero parameters in the input schema, so no parameter documentation is needed. The baseline for 0 parameters is 4.
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 states a specific verb ('run') and resource ('synthetic G2 fixture baseline'), and outlines the pipeline stages. It distinguishes from sibling tools like 'run_audit_gates' and 'run_phase_acceptance' by being a combined run. However, the term 'synthetic G2 fixture baseline' and 'acceptance' could be more clearly defined.
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?
No guidance is provided on when to use this tool versus its siblings, prerequisites, or order of operations. The agent has no information about when this pipeline is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.