cases-update_status

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

With no annotations, the description adds context like automatic timestamping and transition validation, but does not disclose permissions, side effects (e.g., triggering workflows), or error cases.

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?

Two sentences are concise and efficient, though a bullet list for transitions might improve readability. No superfluous text.

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?

The description lacks output details and side effects, but given the tool's straightforward nature and absence of output schema, it is minimally adequate. Validation and timestamp info help.

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%. The description explains the 'status' parameter's valid values and role (CMMN lifecycle status) but adds little beyond the schema for 'case_id'.

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?

The description clearly states the verb 'updates' and the resource 'case's lifecycle status', includes specific transition validation rules, and distinguishes from sibling tools like cmmn-update_task_status.

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?

The explicit transition list implies when to use, but no explicit when-not-to-use or alternative guidance is provided. However, the transition rules serve as clear usage constraints.

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