setProcessVariables

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

No annotations are provided, so the description must fully disclose behavioral traits. While it indicates mutation ('set/update'), it does not specify whether variables can be set after process completion, what permissions are required, or whether the operation overwrites or merges existing variables. This is insufficient for a mutation tool.

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 short sentence, front-loading the core action. It contains no extraneous information, achieving maximal conciseness.

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 and no annotations, the description covers the purpose and parameters minimally. For a simple mutation tool, it might be sufficient, but it lacks details on behavior (e.g., merge vs overwrite, error conditions) that would improve completeness.

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?

The input schema provides 100% parameter descriptions, so the description adds little extra meaning beyond restating 'variables' as 'The variables to set/update'. No additional constraints or format details are given. 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?

The description 'Set/update variables of a process instance' uses a specific verb (set/update) and clearly identifies the resource (variables of a process instance). It distinguishes this tool from sibling tools like 'getProcessVariables' (read) and 'deleteProcessInstance' (delete).

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 description gives no explicit guidance on when to use this tool versus alternatives (e.g., when to use 'setProcessVariables' vs 'startProcessInstance' or 'completeTask'). Usage is implied by the name and description, but no exclusions or alternative suggestions are provided.

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