move_list

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

No annotations are provided, so the description must carry the full behavioral burden. It states the basic action and position format, but does not disclose side effects (e.g., reordering other lists, affecting cards), permission requirements, reversibility, or any constraints. This is a significant gap for a mutation tool.

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 extremely concise: one sentence stating the purpose and a short instruction for a parameter. Every word contributes, and it is front-loaded with the action. No wasted or redundant text.

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?

With 2 parameters and an existing output schema, the description need not explain return values. However, it lacks clarity on the operational context: what actually happens when a list is moved to 'top'/'bottom'/'number' and whether the move affects existing list ordering. The tool is simple but still has notable gaps in context.

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?

The schema has zero description coverage, so the description must compensate. It explains the position parameter with concrete examples ('top', 'bottom', or a number) but leaves list_id self-explanatory without further detail. The meaning of 'number' is ambiguous (e.g., zero-indexed? range?), so compensation is partial.

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 the specific verb 'Move' with the resource 'list' and states the positional outcome ('new position'), clearly distinguishing it from sibling tools like create_list or archive_list. The instruction 'Use top, bottom, or a number' further clarifies the operation.

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?

The description implies usage via the action 'Move a list', but it does not explicitly state when to use this tool over alternatives or provide exclusions. There is no mention of related tools or when not to use it, though the purpose itself is fairly self-evident.

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