MoveTransportObjects

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the operation is a mutation and explains batch-mode recording with empty immediate answers, which is useful beyond the schema. However, it omits permissions, reversibility, error behavior, and what happens to the source task after the move.

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 front-loaded with the core move operation in the first sentence and follows with the position rule and batch behavior. It is efficient and free of filler, though the batch-mode sentence is dense.

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 schema fully documents all four parameters and there is no output schema, so the description need not explain return fields. However, for a mutation tool with no annotations, it should provide more context about permissions, side effects, or failure modes beyond batch recording.

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 100%, so the baseline is 3. The description reinforces that entries are named by their position in the source task's object list, but this mostly repeats the schema's own description and does not add new syntax or format guidance.

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 states a specific verb (moves) and resource (object entries between transport tasks), and it clearly identifies the source and target by parameter names. It is easy to distinguish from sibling tools like AddTransportObject or RemoveTransportObject because it describes moving existing entries rather than adding or removing them.

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 when to use the tool by explaining that it moves entries between tasks, but it does not explicitly say when to choose it over alternatives such as removing from one task and adding to another. No exclusions or prerequisites are stated.

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