update_column

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

The description mentions it's a partial update, specifies validation error condition, and states the success response '{ ok: true }'. While it lacks details on permissions or idempotency, it gives sufficient behavioral context given no annotations are provided.

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 concise with three sentences. The first sentence states purpose, the second provides a constraint, the third redirects to a sibling, and the fourth gives return value. No wasted words.

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?

Given the empty input schema and no output schema, the description is incomplete. It does not enumerate which fields can be updated, lacks details on error responses beyond the validation error, and provides no information about permissions or side effects.

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?

The input schema is empty, but the description implies parameters like column_id and additional fields without specifying names or types. The description provides only vague hints about parameters, missing clarity needed for an agent to construct valid calls.

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 clearly states 'Update an existing Kanboard column (partial update)' with a specific verb and resource. It distinguishes from siblings like create_column, delete_column, and move_column by explicitly mentioning partial update and not for reordering.

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?

It explicitly says 'NOT for reordering — use move_column instead' and warns about VALIDATION_ERROR if only column_id is provided. This provides clear when-to-use and when-not-to-use guidance.

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