Add column

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

Annotations already declare non-read-only, non-idempotent, non-destructive, open-world. The description adds context the annotations don't carry: it returns a column_id, where the column is placed, that editors see it, and that no one is notified. It does not address duplicate-title behavior, which matters for a non-idempotent mutation.

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 tight sentences with the core action and placement front-loaded. The opening fragment ('Empty column on a board, to group cards in a stack') is slightly telegraphic but earns its place by defining the artifact.

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?

With no output schema, the description usefully states the returned column_id and the notification/visibility side effects. Only error handling and duplicate-title semantics are unaddressed for a two-parameter mutation.

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%, with board_id and title already documented in the schema. The description only implies these fields ('titled column', 'on a board') without adding format or constraint detail, so 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?

States a specific verb+resource ('Adds a titled column') plus its function (grouping cards in a stack) and where it lands (top of the Unsorted panel). This clearly differentiates it from siblings like create_board or move_card.

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?

Explains the downstream step explicitly: use move_card with to_column_id to populate the new column, and notes placement on top of Unsorted. No explicit 'when not to use' or alternative, but the workflow context is clear enough to select it correctly.

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