cmmn-create_milestone

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

No annotations provided; description only mentions creation and achievement nature, omitting behavioral details like idempotency, permissions, or side effects. For a creation tool, more transparency needed.

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 concise sentence front-loads core action and key differentiating trait. No wasted words.

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?

No output schema or annotations. Description lacks return value details, error conditions, and relational context (e.g., how milestone fits in CMMN lifecycle). Incomplete for a 6-param creation tool.

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?

Input schema covers all 6 parameters with descriptions (100% coverage). The main description adds no extra parameter info beyond what schema already provides. Baseline score due to high 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 'Creates a CMMN Milestone' and distinguishes it from tasks/stages with '(no work, just achievement)'. Purpose is specific and unambiguous.

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?

Implies use for marking progress without work via 'no work, just achievement', but no explicit when-to-use or alternatives among 100+ sibling tools. No prerequisites or context given.

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