cmmn-reset_task

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

With no annotations, the description carries the full burden. It discloses the audit return, cascade behavior (walks sentry graph), dry_run preview, and retention of existing data. It could mention auth needs or rate limits but is otherwise thorough.

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?

Four sentences with no wasted words. Front-loaded with the main purpose. Each sentence adds essential detail: audit return, cascade, dry_run, and preservation of data.

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?

Given 4 parameters, no output schema, and no annotations, the description covers purpose, return value, and parameter behaviors. It explains cascade and dry_run thoroughly. Minor gaps like edge cases (e.g., invalid task_id) are not addressed, but overall sufficient.

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 is 100%, so baseline is 3. The description adds value by explaining cascade's effect on downstream items and dry_run's preview purpose, beyond the schema descriptions. It provides context for 'to_status' options.

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 'Resets a task to allow re-execution.' Verb and resource are explicit. The description also details the audit return and cascade/dry_run options, distinguishing it from siblings like 'cmmn-reset_stage'.

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?

Description implies usage for re-execution and explains cascade and dry_run, but does not explicitly contrast with alternatives like 'cmmn-execute_task' or provide when-not scenarios. Context is clear but lacks exclusions.

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