update_item

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

Annotations are uninformative (readOnlyHint=false, destructiveHint=false) and the description adds no behavioral context beyond the action itself. It does not disclose whether updates are partial or full, whether fields are overwritten, authentication requirements, side effects, or response behavior.

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 a single concise sentence with no filler. The action and updateable fields are front-loaded, making it easy to parse quickly.

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 9 parameters, no output schema, and minimal annotations, this description is not complete enough for an agent to reliably invoke the tool. It omits partial-update semantics, return values, and any context about the item model, leaving critical decisions to inference.

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 description must compensate. It lists six updateable parameter names (title, description, status, priority, dueDate, tags) but adds no meaning to the required IDs (projectId, boardId, itemId) and does not explain value formats or allowed values for dueDate, status, or priority.

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 a specific verb ('Update') and resource ('item'), and lists the exact fields affected: title, description, status, priority, dueDate, tags. This distinguishes it from sibling tools like update_comment and update_board without needing to open schemas.

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 guidance on when to use this tool versus alternatives such as set_cell, create_item, or update_comment. No prerequisites, context, or exclusions are provided.

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