Reorder or move a checklist item

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

No annotations are present, so the description carries the full behavioral burden. It usefully discloses that `toChecklistId` may target a checklist on another card and how ordering resolves, but says nothing about permissions, what happens on invalid/stale ids, or whether the operation is reversible.

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?

Two sentences, front-loaded with the action and scope, followed by the ordering rules. No filler and no repetition 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 four-parameter mutation with no annotations and no output schema, the description covers the non-obvious parts: cross-checklist/cross-card targeting and the before/after/omitted ordering resolution. It leaves failure modes and side effects unstated, which is the main remaining 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 coverage is 50%: `beforeId`/`afterId` are already described in the schema and the description only reinforces them, while `id` and `toChecklistId` are undocumented in the schema. The description adds genuinely new meaning for `toChecklistId` (cross-card) and the one-or-none rule for before/after, but leaves `id` implicit.

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 ('Move a checklist item') plus the two distinct scopes it covers: within its own checklist or into another checklist. An agent can distinguish this from kanbini_update_checklist_item or kanbini_add_checklist_item from the description alone.

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?

Clearly specifies the operating conditions: one of `beforeId`/`afterId` suffices, and omitting both appends to the end. It does not, however, state when to prefer this over the sibling `kanbini_update_checklist_item` (rename/edit) or that `toChecklistId` is required even for same-checklist reordering.

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