Edit Tracker board column

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety is largely covered. The description still adds real behavioral value: partial-update semantics ("only the fields set in `body` are changed") and the return shape ("Returns the updated column"), which the annotations do not convey.

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 short sentences, no waste, and the core semantics (partial edit) are front-loaded ahead of the ID-sourcing hint and the return note.

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 3-required-param mutation with a nested body object and no output schema, the description covers the key points an agent needs: partial update behavior, where the column_id comes from, and what is returned. Missing only finer details such as the effect of replacing `statuses` or permission requirements.

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 the nested `body` schema already documents each field and states that every field is optional and only set fields are sent. The description's partial-update sentence restates that schema text rather than adding new meaning, so the baseline 3 applies.

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 names a specific verb and resource ("Edit a board column") and scopes the change to fields supplied in `body`, which separates it from the sibling create/delete/list/get column tools. It stops short of explicitly naming those siblings, but the operation is unambiguous.

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?

"Get `column_id` from `columns_list`" is a concrete workflow hint for obtaining a required identifier, which is more than nothing. However, there is no guidance on when to use this versus `tracker_columns_create`/`tracker_columns_delete`, no prerequisites, and no exclusions.

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