update_item

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

The annotations (readOnlyHint=false, destructiveHint=false) only confirm that this mutates without destroying; the description adds no behavioral context on top of that. It does not disclose partial-update semantics, whether omitted fields are preserved, validation of status/priority values, or what happens if the item does not exist. For a mutation tool, an agent cannot predict side effects from this text.

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 one-sentence description is front-loaded with verb and resource and contains no filler; every word earns its place. The compact parenthetical field list works as a quick reference for the 6 mutable fields. It is appropriately sized given the schema carries the detailed parameter documentation.

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 9-parameter mutation tool with no output schema, this description is too thin: it omits partial-update semantics, the distinction from set_cell, and any expectation about results or errors. The rich input schema is not enough to make the tool safely invokable without behavioral context. The three required IDs (projectId, boardId, itemId) are at least documented in the schema.

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 100%, and individual descriptions are informative (e.g., status values, dueDate ISO 8601 format, projectId provenance from list_projects). The description's field list is a helpful at-a-glance overview but adds no meaning beyond the schema. Baseline 3 applies because the schema does the heavy lifting.

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?

"Update item fields" states a specific verb and resource, and the parenthetical enumerates exactly the mutable fields (title, description, status, priority, dueDate, tags), making its purpose obvious against create_item and delete_item. It falls short of 5 because it does not differentiate from set_cell, which also modifies item data.

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 guidance is given on when to use this tool versus alternatives: set_cell for single-cell updates, create_item for new items, or update_board for board-level settings are never mentioned. An agent must infer usage entirely from the tool name and sibling list; no prerequisites or when-not conditions are stated.

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