Move Card

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

With no annotations, the description carries the burden and does disclose one non-obvious behavior: 65535 means end of list. However, it does not mention validation failures, whether same-list moves are allowed, or any side effects, and the schema default of 65536 creates confusion about the intended sentinel.

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?

Two short sentences with the action front-loaded and the non-obvious position value placed second. No filler or repetition of schema details.

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?

The tool is simple and has an output schema, but zero annotations and zero schema parameter descriptions leave too much unsaid. The 65535/65536 discrepancy is exactly the kind of ambiguity that can cause an agent to pass the wrong position value, so the definition is not fully trustworthy.

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 description coverage is 0%, so the description must explain the parameters. It only clarifies position with the end-of-list sentinel; id and listId are left to name inference, and the position semantics are incomplete because the description's 65535 conflicts with the schema default of 65536.

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 a specific verb ('Move'), resource ('card'), and destination ('another list') plus position, making it immediately distinguishable from siblings like update_card, duplicate_card, and delete_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?

There is no explicit guidance on when to choose this tool over update_card or duplicate_card, and no exclusions or prerequisites. The only usage hint is the position sentinel, which addresses parameter use rather than tool selection.

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