yougile_update_column

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

Annotations already indicate destructiveHint=true, and the description adds valuable context by specifying that deletion is a 'soft-delete' and that moving to another board is supported. This goes beyond the schema's bare parameter docs, though it does not detail side effects on associated tasks.

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 a single, concise sentence that front-loads the primary action and lists the main update targets. Every word adds value, with no unnecessary detail or repetition.

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 update operation with a well-defined schema and annotations, the description is sufficiently complete. It identifies the resource, the mutable fields, and the special 'soft-delete' behavior. No output schema is needed, and the lack of edge-case details is acceptable for this tool.

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 schema covers all parameters with descriptions (100% coverage), and the tool description essentially restates the schema's parameter meanings (e.g., boardId = 'move to another board', deleted = 'soft-delete'). The description adds no extra semantics beyond grouping operations, so it meets the baseline for high schema coverage.

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 a specific action ('Update a column') and enumerates the exact fields and operations (title, color, move to another board, soft-delete). This distinguishes it from sibling tools like create_column, list_columns, get_column, and update_task.

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 implies usage by stating what the tool does, but it gives no explicit guidance on when to use it versus alternatives like create_column or update_board. No exclusions or prerequisites are mentioned, so the usage context is only implied.

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