Create a list (column)

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

With no annotations, the description does disclose two real behavioral facts: the new list is appended at the right end, and the call returns { id, boardId }. It does not cover permissions/authorization, whether the name must be unique on the board, or failure modes for an invalid boardId, which matters for an unannotated mutation tool.

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 short sentences, front-loaded with the action and placement, then chained consequences. No filler or restatement of the title.

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 tool with no output schema, the description supplies the return shape, the append position, and the id-chaining needed for follow-up calls. Only permission/error behavior is missing, which is a modest gap.

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 0%, so the description must carry the load. It usefully explains the provenance of boardId, but the 'name' parameter is left entirely to the schema's minLength:1 with no note on uniqueness, trimming, or length limits.

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 and resource ('Create a new list (column)') plus the exact placement semantics ('at the right end of a board'), which also implicitly distinguishes it from kanbini_move_list and kanbini_update_list. An agent knows precisely what effect the call has without opening the schema.

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?

Gives concrete workflow context: where boardId comes from (kanbini_list_boards or a fresh kanbini_create_board) and how the result feeds kanbini_create_card. It stops short of saying when not to use this tool, e.g. when a similar column already exists or that update_list/move_list handle modification.

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