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

Annotations include destructiveHint=true, so the description doesn't need to repeat that. However, it adds useful context: how to clear the title (empty string) and that lanes are identified by index. It doesn't mention that it modifies a board state or any required access, but annotations cover the destructive nature. The description adds some value beyond annotations but not much.

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 two sentences, concise, and front-loaded with the main purpose. Every sentence adds value, with no fluff.

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 mutation tool with no output schema, the description provides enough context: it explains the operation, how to clear the title, and directs to list_tasks for reading. The description is complete enough given the annotations and schema. Slight deduction for not mentioning any side effects beyond the title change, but annotations cover destructive hint.

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 coverage is 80%, and the description adds meaning: it explains that the 'title' parameter with an empty string clears the lane title, and it explains the 'lane' parameter as a row index. It doesn't cover 'author' or 'access_key' but those are covered by schema descriptions. The description enhances the understanding of the 'title' and 'lane' parameters.

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 what the tool does: 'Set (or clear) the title of a kanban row (lane)'. It specifies the resource (lane), the action (set/clear title), and distinguishes from siblings like set_column_width and create_column. The purpose 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?

It explains how lanes are identified (by integer index) and mentions that passing an empty string clears the title. It also references list_tasks for reading current lane titles, which implies when you might use this tool versus list_tasks. However, it doesn't explicitly state when NOT to use this tool, but the context is clear enough.

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