ds_resume_process_instance

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

With no annotations, the description carries the full burden of disclosing behavior. It simply states the action 'Resume' but does not mention side effects, permissions, idempotency, error conditions, or whether it only works on paused instances. The word 'paused' adds a minor constraint but lacks depth.

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?

The description is a single, front-loaded sentence with no filler. It is appropriately concise for a simple action and contains only the essential verb and object.

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 a tool with 2 required parameters, no output schema, and no annotations, the description is too sparse. It lacks parameter explanations, usage context, and behavior details. The minimalism is not sufficient to guide an agent effectively, especially with many sibling workflow-management tools.

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 description coverage is 0%, so the description must compensate. It does not explain the role of project_name or process_instance_id beyond their names. The phrase 'workflow instance' loosely maps to process_instance_id, but project_name is completely unaddressed. No meaning is added beyond the schema.

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 uses a specific verb 'Resume' and clear resource 'workflow instance', stating exactly what the tool does. It does not explicitly compare with sibling tools like ds_pause_process_instance or ds_stop_process_instance, but the 'paused' qualifier helps differentiate from those.

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 is provided on when to use this tool vs alternatives. The phrase 'paused workflow instance' implies a precondition, but there is no explicit context or exclusions. The description gives no indication of when not to use it or how it differs from rerun operations.

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