fizzy_move_card

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It implies a mutation operation but does not explain side effects, permissions, or what makes the columns 'special' in terms of behavior. The mention of 'special columns' raises questions that are left unanswered.

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 (~20 words) that front-loads the action and contains no redundant or extraneous information.

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 mutation tool with no annotations and no output schema, the description is incomplete. It does not explain what happens when moving a card to 'done' or 'not_now' (e.g., archiving, closing, or other side effects), nor what the tool returns after the operation. The agent is left to infer critical behavioral details.

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 already provides 100% coverage with clear descriptions for both parameters (card_id and column). The tool description adds minimal semantic value beyond reinforcing the special column options, meeting the baseline of 3 for high schema coverage.

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 resource 'card' and destination 'column', clearly distinguishing it from sibling tools like update_card or get_card. The added detail about special columns ('done'/'not_now') further clarifies the tool's specific purpose.

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 provides clear context: it is for moving a card to a different column, with explicit guidance for using 'done' or 'not_now' for special columns. However, it does not mention when to use this tool over alternatives such as update_card, nor exclusions for when not to use it.

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