workflow_complete_task

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

With no annotations provided, the description carries the full behavioral burden but stays silent. It does not say this is a state-mutating operation, what happens on a version mismatch (the presence of expectedVersion implies optimistic concurrency but this is never explained), whether the advance is reversible, or what permissions/approvals are needed.

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?

A single compact sentence with no filler, so it is not verbose. However, its brevity comes at the cost of clarity — the sentence is dense with undefined internal terminology rather than being front-loaded with the actual effect.

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 mutating workflow tool with no annotations, no output schema, and two undocumented required parameters, the description is insufficient. It should at minimum state the mutation, the version-conflict behavior, and the resulting task state; none of that is present.

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% and neither taskId nor expectedVersion is mentioned in the description. The phrase 'current local result' loosely gestures at a versioning concept but never explains that expectedVersion guards against stale writes, which is the single most important thing an agent must understand here.

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 abstract jargon ('confirm the current local result', 'advance it to its next persisted gate') rather than stating plainly that it marks a task complete. It never names the resource (task) or distinguishes this from close siblings like workflow_task_skip or workflow_ticket_advance. An agent would have to guess what 'persisted gate' means.

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 when-to-use guidance and no exclusions. Given ~37 sibling tools including workflow_task_skip, workflow_ticket_advance, and workflow_submit_decision, the description offers nothing to help choose between them. The only implicit usage signal is the word 'complete'.

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