create_kanban_board

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

With no annotations, the description carries the burden of explaining side effects. It discloses that a .excalidraw file is generated and an absolute path is returned, but it does not explain where files are written by default or whether existing files are overwritten.

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 well organized with an overview, an Args block, and a Returns line. It is concise and free of filler, though the 'Great for visualizing...' sentence adds a bit of promotional language that could be trimmed.

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?

The core behavior and return value are covered, and the output format is explicitly stated. It lacks detail on default output_path behavior and the nested column color option, leaving some ambiguity for an agent trying to invoke the tool fully correctly.

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 compensates by listing each parameter and its meaning. However, it omits the 'color' property available on each KanbanColumn, and it does not indicate which parameters are required beyond inferring from the schema.

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 uses a specific verb-resource pair ('Create a Kanban board diagram') and elaborates with 'column-based task board with cards in each column,' which clearly distinguishes it from sibling diagram tools like flowcharts or sequence diagrams.

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 states the tool is 'Great for visualizing workflows, sprints, and task status,' giving an agent context on when to select it. It does not explicitly mention alternatives or exclusions, but the intended use case is reasonably clear.

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