workflow_request_approval

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

No annotations are supplied, so the description carries the full burden. It reveals that this is a write operation recording an approval, but says nothing about immutability, idempotency, required permissions, or what happens when the supplied versions do not match the current state (the optimistic-lock semantics implied by expectedTaskVersion).

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 front-loaded sentence with zero filler and the action stated first. It is tight to the point of being underspecified for a four-parameter mutation, but nothing in the sentence is wasted.

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 four-required-parameter mutation with no annotations, no output schema, and no parameter descriptions, the definition is too thin. It omits the version-guard behavior, who may call it, and what recording an approval causes downstream, all of which an agent needs before invoking it correctly.

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% across four required parameters, so all semantic burden falls on the description. It gestures at 'exact artifact and task version' but never explains the distinction between artifactVersion and expectedTaskVersion, nor that the latter acts as a concurrency guard, leaving two of four parameters effectively undocumented.

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?

States a clear verb+resource ('Record a human approval') and the scoping object ('an exact artifact and task version'), so the agent knows the action writes an approval record rather than computing status. It does not, however, distinguish itself from closely related siblings like workflow_submit_decision or workflow_epic_approve_change_request, leaving the reader to infer which approval surface this applies to.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives among the many approval/decision siblings. The phrase 'human approval' weakly implies a human rather than agent is the approver, but no condition or exclusion is stated.

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