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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation profile is covered. The description adds genuinely new behavioral context — the optimistic-locking requirement to supply the current lock_version — but does not say what happens on a stale lock_version (conflict/error) or which permissions 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?

One front-loaded sentence with no filler; the editable fields come first and the lock_version prerequisite follows. It is arguably too sparse for a 5-parameter mutation tool, but nothing 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?

An output schema exists, so return values need not be described. Still, for a write tool with 5 parameters at 0% schema coverage, the description omits the id parameter's role, valid status values, and conflict behavior when lock_version is stale.

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 schema contributes nothing beyond names and types. The description names three of the five parameters and explains that lock_version must be read first, which is meaningful, but leaves 'id' and 'status_id' semantics (valid status values, project scoping) 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 specific verb (Edit) with the concrete editable fields (subject, description, status) on a work package, so the agent knows exactly what operation it performs. It does not distinguish itself from close siblings such as openproject_update_wiki_page or openproject_create_work_package.

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 clause 'after reading the current lock_version' functions as a real prerequisite (read before edit), which is useful context. However, there is no statement of when to prefer this over update_wiki_page, nor any exclusion of cases where editing is inappropriate.

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