Remove an acceptance criterion from a goal. Grove mode: only while goal is in backlog (frozen once started). Standard mode: until goal is done. Cascades to all evidence on the criterion. Returns confirmation with removed criterion details.
| Name | Required | Description | Default |
|---|---|---|---|
| criterionId | Yes | UUID acceptance criterion |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructive and idempotent behavior. The description adds important context: the removal cascades to all evidence on the criterion and returns confirmation with removed criterion details, which goes beyond the annotation-only picture.
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?
Three sentences, each carrying distinct information: action, mode restrictions, and cascade/return. No filler or redundancy.
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 single-parameter tool with no output schema, the description covers the action, validity window, side effects, and response. This suffices for an agent to correctly invoke it.
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?
The schema already fully describes criterionId as a required UUID. The description adds no additional parameter-specific meaning, so baseline 3 applies given 100% schema coverage.
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 clearly states 'Remove an acceptance criterion from a goal' with a specific verb and resource. It distinguishes from sibling remove tools by targeting criteria specifically, and correctly contrasts with goal-update-criterion.
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?
Provides explicit timing constraints: in Grove mode only while goal is in backlog (frozen once started), and in standard mode until goal is done. This gives when/when-not context, though it doesn't name alternative tools for other object types.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clear distinct purposes (goal-create vs goal-update vs goal-delete), but the evidence-related tools (goal-add-evidence-text, goal-attach-evidence, goal-request-upload) and note tools (goal-add-note) have overlapping concepts that require careful reading of descriptions to differentiate. Overall, the detailed descriptions help resolve ambiguity, but a few tools could be easily confused.
The majority follow a consistent verb_noun pattern with a resource prefix (goal-create, goal-get, project-list, project-update). However, there are deviations like account-delete (noun-verb reversed), goal-todo, goal-summary, goal-tree, and goal-recent-unresolved that break the pattern. The inconsistency is minor but noticeable.
With 38 tools, this server has a very large surface area. Even for a complex planner with evidence management, the number exceeds the 25-tool threshold for 'too many'. Many tools could potentially be consolidated (e.g., goal-add-note and goal-add-evidence-text), and the size may overwhelm agents during tool selection.
The tool set provides complete coverage of the domain: full goal lifecycle (create, get, update, delete, list, tree, move, reorder, block), evidence management (attach, request upload, text evidence, remove), acceptance criteria (add, update, remove, request change, resolve escalation), assumptions (add, update, remove, suggest, attach evidence), blockers, notes, project management (CRUD, dependencies), and configuration settings. No critical gaps are apparent.