monday_move_item_to_group

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

Annotations already declare readOnlyHint=false and destructiveHint=true; the description adds context about the governed-connector authority and write-approval flow ('approval_ref: Approved platform task UUID when resuming a write', 'effect: Claimed read or write effect; Spring verifies it'). This is useful but does not disclose the actual side effects of moving an item (e.g., what changes or what could be destroyed). No contradiction with annotations.

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 compact and well-structured with an Args list, and every line is short. It contains some generic filler (the routing sentence) and repeats the operation name, but overall it is efficiently organized and easy to scan.

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?

Although an output schema exists, the input side is incomplete: the actual connector arguments are hidden inside an opaque JSON string with no example or field breakdown. The description doesn't explain how routing, project_id/project_ref, or approval_ref interact for this particular operation, so a correct invocation cannot be derived from the provided information.

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 description gives one-line glosses for all seven wrapper parameters, but the critical `arguments` parameter is only called 'JSON string of arguments for the connector operation'—it never specifies the required JSON structure for moving an item to a group (e.g., item_id, group_id, board_id). Given 0% schema description coverage, the description fails to compensate with operation-specific payload details, so an agent cannot reliably construct a valid call.

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 opens by restating the tool name as 'Monday connector operation move_item_to_group' and adds only a routing constraint ('Routes only through the exact project/account governed connector authority'). It never states in plain language that the tool moves a Monday.com item to a different group, leaving the agent to infer purpose from the name alone. This is close to a tautology.

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 when-to-use guidance is given. The description does not mention when to choose this over related Monday tools such as monday_update_item or monday_change_column_value, nor does it state prerequisites like needing a project/account authority. The routing sentence is an invocation constraint, not a usage guideline.

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