cmmn-create_stage

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

No annotations provided. Description only states creation and purpose, lacking details on side effects, required permissions, lifecycle impact, or return value. Minimal disclosure for a mutation tool.

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?

Single sentence, front-loaded with verb and resource. No superfluous words, but could benefit from slightly more context on usage or output.

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 an 8-parameter creation tool with no output schema and no annotations, the description lacks explanations of return value, error conditions, or prerequisites (e.g., case_id must exist). Incomplete for the complexity.

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 coverage 100% with descriptive parameter descriptions (e.g., auto_complete, status). Tool description adds no additional meaning beyond grouping purpose, 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?

Description states verb 'creates' and resource 'CMMN Stage' with purpose 'grouping related plan items'. Clearly identifies the tool's function but does not differentiate from sibling tools like cmmn-create_task or cmmn-create_milestone.

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 on when to use this tool over alternatives (e.g., create_task, create_milestone). No context on prerequisites or conditions for grouping.

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