cmmn-get_next

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

Without annotations, description reveals return content (context, prompt, result_schema) and task type distinction. However, no mention of side effects, error handling if no next task, or required permissions.

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, no fluff. First sentence states purpose, second details return fields, third clarifies behavior for human vs process tasks.

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?

With no output schema, description adequately explains return structure. Lacks error conditions or prerequisites, but sufficient for a low-complexity tool with one parameter.

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?

Description adds no additional meaning beyond input schema's case_id description. Schema coverage is 100%, so baseline 3 is appropriate.

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 uses specific verb 'Gets' and resource 'next task to execute in a case workflow'. Clearly distinguishes from sibling task management tools by specifying 'next' and detailing return content for human vs process tasks.

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 explicit when-to-use or when-not-to-use guidance. Implies usage in case workflow progression but does not compare to alternatives like cmmn-get_execution_plan or cmmn-list_items.

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