set_cell

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the write behavior is expected. The description adds that this operation sets a single cell, which clarifies the scope of mutation, but it does not disclose what happens to prior values, formatting requirements, or whether the operation is reversible. No contradiction with annotations.

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 one tight, front-loaded sentence with no filler. The word 'single' is meaningful because it scopes the operation precisely, and every word earns its place.

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 simple setter, the description covers the core intent and required IDs, but it omits important guidance on how to format values for different column types and what the response looks like. Given the sibling tool get_board_schema exists, the description could usefully point to it for column-specific value formats, but it does not.

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 only 20%, so the description must carry extra weight. It explains the core roles of itemId and columnId (operating on an item, by column), and 'value' is partially described in the schema. However, projectId and boardId are not individually clarified, and no concrete value-shape examples are provided beyond the generic warning that the shape depends on column type.

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 uses a specific verb ('Set'), a precise resource ('single cell value on an item'), and a clear locator ('by columnId'). This distinguishes it from broader sibling tools like update_item, since it targets one cell rather than an entire item.

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 phrase 'single cell value' implies this is for cell-level updates as opposed to broader item updates, but the description never explicitly states when to use this tool versus alternatives like update_item. There is no exclusion guidance or mention of prerequisites.

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