Move Basecamp Todo List Group

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

Annotations already indicate non-destructive, idempotent behavior. The description adds important domain context: groups always render after ungrouped todos, and the cross-list restriction. It doesn't mention pagination or return format, but these are less critical here.

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, each earning its place: the action, a rendering constraint, and a tool reference plus a hard limitation. Front-loaded with the core operation, no filler.

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 move operation with full schema and annotations, the description covers the essential constraints and where to get IDs. It could briefly mention that the operation affects ordering only, but is nearly complete.

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%, so the schema already documents parameters thoroughly. The description adds the rule about using basecamp_list_todos for IDs, which is useful, but doesn't add much beyond the schema's own placement semantics. Baseline 4 is reasonable given the high schema quality and the small added guidance.

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 states a specific verb (move) and resource (todo list group/section), and clarifies the scope: 'to a different place among the groups of its todo list.' It distinguishes from basecamp_move_todolist, but doesn't explicitly name it as the sibling to avoid, leaving some differentiation implicit.

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 gives a clear usage constraint ('You cannot move a group to a different todo list') and points to basecamp_list_todos for obtaining group IDs, which is helpful. However, it doesn't explicitly state when to prefer this tool versus basecamp_move_todo or basecamp_update_todolist_group (not a sibling), so alternative routing is only partially addressed.

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