Move Item to Group

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

The description only says 'Move an item', which adds little beyond the annotations. Annotations already indicate non-readonly, non-destructive, and idempotent behavior. The description does not elaborate on side effects, reversibility, or any other behavioral traits.

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 a single concise sentence that is front-loaded with the core action. It is appropriately brief but lacks detail; however, for such a simple tool, conciseness is acceptable.

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?

Given no output schema and simple parameters, the description fails to mention return behavior, permissions, or the effect on the item's other data. It is insufficient for an agent to fully understand the tool's behavior beyond the basic action.

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% with parameter descriptions, so baseline is 3. The tool description does not add extra meaning beyond the schema. The parameter description for 'itemId' is slightly misaligned (mentions 'update' instead of 'move'), but the tool description does not rectify this.

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 clearly states the verb 'move', resource 'item', and destination 'group in a monday.com board'. It distinctly identifies the operation and differentiates it from sibling tools like 'change_item_column_values' or 'move_object'.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites, constraints, or situations where this tool should or should not be used.

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