Move Kanban Card

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

Annotations already indicate non-readonly and non-destructive behavior. Description adds minimal behavioral context beyond 'move', not disclosing side effects, ordering impacts, or idempotency considerations.

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?

Single sentence, no fluff, clear and front-loaded with purpose. Every word earns its place.

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?

No output schema, minimal description. Does not explain return value, error conditions, or scope limitations (e.g., same bucket). Adequate but leaves gaps for a move operation.

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?

Input schema provides basic descriptions for all 4 parameters. Description adds no additional semantics beyond mentioning 'column and/or position', which aligns with schema. Baseline 3 as schema coverage is 50%.

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 clearly states verb 'move' and resource 'kanban card', with specific aspects 'different column and/or position'. This distinguishes it from sibling tools like basecamp_create_kanban_card (create) and basecamp_update_kanban_card (update).

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?

Description implies usage for moving cards but does not explicitly state when to use this tool vs alternatives (e.g., update for changing card details, or other operations). No guidance on when not to use it.

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