Rename or move a board

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

Annotations cover the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the bar is lower. The description still adds real context beyond that: it is a partial/patch update where unspecified fields are preserved, board content is untouched, and it returns a confirmation plus the board address. It stops short of detailing failure modes, but that is a minor gap given the annotation coverage.

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?

Three short sentences, front-loaded with the operations, then the partial-update rule, then the routing to sibling tools. Every sentence earns its place with no restatement of the name or annotations.

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?

There is no output schema, and the description fills that gap by stating 'Returns a confirmation and the board address.' Combined with the patch semantics and sibling routing, an agent has everything needed to select and call this tool correctly.

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%, so baseline is 3. The description maps intent to parameters (rename→title, move→folder, color/icon) but adds no format or syntax details beyond the schema, and does not mention the special 'open' board value that the schema documents. Adequate, but 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?

States specific verbs and resource: 'Rename a board, move it to a folder, or change its color or icon in the sidebar.' It also explicitly carves out the content-editing scope and routes it to update_nodes/update_items, so an agent can distinguish it from sibling tools without opening a schema.

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 gives explicit alternatives: '(to edit content use update_nodes or update_items)', which is exactly the boundary an agent needs when choosing between metadata edits and content edits. No exclusions left to inference for the primary fork, and the partial-update rule ('Only the fields you pass change') tells the agent how to invoke it.

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