Run an end-to-end software development workflow from one requirement: plan, design, implement, test, and review.
Execute complete development workflow: planning → architecture → implementation → QA → review
| Name | Required | Description | Default |
|---|---|---|---|
| language | No | Programming language (default: typescript) | typescript |
| requirement | Yes | The feature requirement to implement (min 10 characters) | |
| include_tests | No | Include test generation (default: true) |
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It reveals only the ordered phases; it says nothing about runtime/latency, whether it writes files or mutates state, permission needs, or what artifacts it returns — critical gaps for a multi-stage orchestrator with no output schema.
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 zero waste, using the arrow chain to compactly convey sequence. It is efficient, though it is arguably too terse for the complexity of the operation.
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 high-complexity orchestration tool with no annotations, no output schema, and no side-effect or result information, the description is insufficient. An agent cannot anticipate cost, duration, or outputs before committing to this broad multi-stage call.
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 100%, with defaults and constraints documented inline (typescript default, min 10 chars, include_tests default true). The description adds no parameter-level meaning beyond the schema, so baseline 3 applies.
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?
States a specific verb ('Execute') and resource ('complete development workflow') and enumerates the phases (planning, architecture, implementation, QA, review), which maps onto the sibling stage tools. It is clear what the tool does, though it never names those siblings or clarifies the distinction explicitly.
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 'complete workflow' framing implicitly signals use when an agent wants the entire pipeline rather than a single stage, but there is no explicit when-to-use, when-not-to-use, or alternative (e.g. the per-stage siblings). Usage must be inferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.