tc_move_item

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

The description goes well beyond annotations by disclosing that moving a folder moves its entire subtree, permissions may change through inheritance, and the write flag is required. It also provides a sample return structure, giving the agent a clear picture of the tool's side effects and output.

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 concise, well-organized with an Args and Returns section, and every sentence provides necessary information. It avoids redundancy and is easy to parse.

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's moderate complexity and the presence of an output schema, the description covers all essential aspects: prerequisites, behavior, parameters, and return value. It also explains edge cases like subtree movement and permission inheritance, making it complete for an agent's decision-making.

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 Args section adds significant meaning over the bare schema: it explains each parameter's role, specifies that item_type defaults to 'FOLDER' and accepts 'FOLDER'/'FILE', and clarifies which parameters are required. This fully compensates for the 0% schema description 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 starts with a clear, specific verb-resource pairing: 'Move a folder or file into another folder.' It also outlines the key arguments and distinguishes this operation from sibling tools like copy or rename, making the tool's purpose immediately obvious.

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 explicitly states the prerequisite 'Requires TC_ENABLE_WRITE=1' and notes important behavior (moving a folder moves its whole subtree, permissions may change). While it doesn't explicitly mention alternatives, the action is clearly scoped to moving, so an agent can infer when to use it.

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