plane-work-item-update

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Update' which implies mutation, but fails to disclose side effects, authentication requirements, or what happens with invalid or missing parameters. The schema provides parameter details, but the description lacks additional behavioral context.

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 extremely concise with two short sentences. It is front-loaded with the primary purpose and immediately follows with a clarifying usage guideline. There is no redundant or unnecessary content.

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?

Given the tool has 12 parameters and no output schema, the description is minimal. It covers the essential update behavior but lacks context on return values, authentication, or typical usage patterns. The high schema coverage compensates somewhat, but completeness is average for a moderate-complexity tool.

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 92%, so the schema already documents parameter details. The description adds valuable semantic insight with 'Only include fields you want to change', indicating a partial update (PATCH-like behavior). This goes beyond what the schema provides, meriting a score above baseline.

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 the verb 'Update' and the resource 'a work item'. It distinguishes the tool from siblings like plane-work-item-create or plane-work-item-delete by specifying the update operation. The additional note 'Only include fields you want to change' further clarifies partial update semantics.

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 provides a general usage hint about including only changed fields, but it does not explicitly state when to use this tool versus alternatives (e.g., create, delete) or mention any prerequisites or restrictions. There is no guidance on when not to use it.

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