fluig_process_start

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

With no annotations provided, the description carries the full burden. It includes upfront 'WRITE' to denote mutation, and provides critical behavioral details: cardData replaces (not merges) and completeTask behavior (true moves, false parks). It could additionally describe error handling or async behavior, but the given details are substantial.

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 three sentences, each earning its place: verb+resource, key parameter explanations, and a prerequisite role requirement. It is front-loaded with the action type and purpose, with no fluff.

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 6 parameters and no output schema, the description covers core functional aspects (write operation, replacement behavior, state targeting, completion mode). It lacks return value or error details but is adequate for invocation given good schema documentation.

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 beyond the schema by clarifying that cardData must send all fields (no merge) and explaining completeTask's default and effect. This enhances understanding of parameter behavior.

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 'Start a process instance' with a specific verb and resource. It also explains key parameters cardData and choosedState, distinguishing this tool from siblings like move, take, or cancel which handle different lifecycle actions.

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 mentions the prerequisite that 'The configured user needs the start role,' but does not provide explicit guidance on when to use this tool versus alternative process tools. Usage context is implied by the naming and verb, but no exclusions or alternatives are listed.

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