roiq_move_card

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the basic action ('moves a card'), omitting side effects (e.g., whether it modifies other records), permissions required, or reversibility. For a mutation tool, this is insufficient.

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, front-loaded sentence with no wasted words. It is efficient but lacks necessary details, making it borderline under-specified.

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 the tool has 2 required parameters, no output schema, and no annotations, the description is incomplete. It does not explain the return value, error conditions, or required state (e.g., card must exist). An agent would be unsure of the outcome.

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 input schema has 2 parameters with 0% description coverage. The description adds minimal meaning: 'code' is likely a card identifier and 'status' the target column/state. However, it does not explain the format of 'code' or acceptable values for 'status', leaving the agent to guess.

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 action ('moves a card') and the target ('to another column/state'), which differentiates it from siblings like 'roiq_add_card' (adds a new card) and 'roiq_list_cards' (lists). However, it could be more precise about the exact effect (e.g., changing 'status' or 'column' field) and how it differs from 'roiq_update_card'.

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 the tool is used for moving a card to a different column or state, but it provides no explicit guidance on when to use this tool versus alternatives like 'roiq_update_card'. There is no mention of prerequisites or exclusions.

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