move_swimlane

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

No annotations given, but description clarifies operation is only ordering changes, returns success object with ok: true, swimlane_id, position. Does not mention side effects on other swimlanes but sufficient for a simple move.

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 sentences: purpose, parameter requirements, scope and return. Front-loaded, no wasted words.

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 tool with two params and no output schema, description covers key aspects. Lacks mention of potential reindexing of other swimlanes, but overall complete enough.

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 100%, and description adds value by emphasizing position is 1-based and required with no default, which supplements 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?

Description states specific verb 'Reorder' and resource 'swimlane within a Kanboard project', clearly distinguishing from siblings by noting rename uses update_swimlane.

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?

Explicitly states required parameters and that no default exists, and provides alternative for rename. Could further differentiate from move_column or move_task_position but is adequate.

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