Edit Tracker board

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description still adds real value beyond that: omitted fields are left unchanged (PATCH semantics) and ``columns`` is a wholesale replacement rather than a merge, plus it states the return value.

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?

Two tight sentences, front-loaded with the mutation semantics before the field enumeration. No filler, no restatement of the title, and the return-value note is a single clause.

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 two-parameter partial-update tool with a fully documented nested schema, the description covers mutation semantics, editable surface, and the return value even though no output schema exists. It is complete enough to call correctly; only the relationship to sibling board/column tools is unaddressed.

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%, including the nested body and column item fields, so the schema already carries the parameter documentation. The description only summarizes the same field groups at a higher level, adding the useful nuance that ``columns`` replaces the layout, but nothing about formats or constraints.

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 states a specific verb and resource ("Edit an agile board") and enumerates the editable surface (name, backlog_available/sprints_available, columns layout). It is clear on its own, but it never names a sibling, and the columns-replacement capability overlaps confusingly with tracker_columns_update in the sibling list.

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?

Usage is only implied: an agent can infer this is the tool for modifying an existing board's name/backlog/sprint/column settings, and the partial-update semantics are stated. There is no explicit when-to-use versus tracker_boards_create, tracker_columns_update, or tracker_boards_delete, and no prerequisites or permission guidance.

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