Convert an architecture decision and deliverables into a delivery checklist with validation gates to track implementation steps and verify completion.
Turn an architecture decision into a delivery checklist with validation gates.
| Name | Required | Description | Default |
|---|---|---|---|
| decision | Yes | ||
| deliverables | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | ||
| stages | No | ||
| sources | No | ||
| decision | No | ||
| validated | No | ||
| limitation | No | ||
| deliverables | No |
Changes observed during successful MCP inspections.
v0.4.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds only a hint about output shape ('validation gates'), which the output schema already carries — no disclosure of limits, failure modes, or what the checklist guarantees.
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. Its brevity costs specification rather than being wasteful, but as structure it is clean.
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?
An output schema covers return values, but the description says nothing about the two required inputs or when the tool applies, so an agent must guess at argument content and at how this differs from planning siblings.
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% for two required parameters. The description never explains what a 'decision' string should contain (a slug, prose, a reference ID?) nor the granularity expected of 'deliverables' (max 30 items). With zero schema documentation, the description needed to compensate and does not.
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 concrete transformation (architecture decision -> delivery checklist with validation gates), which is a recognizable verb+resource and is distinguishable from siblings like decision_record or migration_plan. It falls short of 5 because it never mentions the two inputs that define the operation, leaving the scope slightly abstract.
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 guidance on when to use this versus decision_record, migration_plan, or requirements_check — all plausible neighbors in the sibling list. No prerequisites or exclusions are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.