Move DataLens collection

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

Annotations already declare readOnly=false, destructive=false, and idempotent=false, so the safety profile is covered. The description adds no new behavioral context beyond the schema — it does not mention permission/access-binding effects, required roles, or what happens to existing entry locks when a collection is relocated.

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?

A single front-loaded sentence with zero filler; the core action and the default-destination rule are stated immediately.

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?

With annotations present and no output schema, the essentials for calling the tool are covered. However, for a mutation that relocates a container, the description omits any note about permission inheritance or side effects, which an agent would want before invoking it.

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 schema already documents collection_id, parent_id, and title. The description's root-when-omitted note merely restates the parent_id schema description, adding no syntax or format detail.

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 and resource ('Move a collection') plus the destination scope, which is clear enough to distinguish it from read/update siblings like datalens_collections_get or datalens_collections_update. It does not, however, differentiate itself from the near-neighbor datalens_collections_move_bulk or datalens_workbooks_move.

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 only conditional given is about parent_id behavior ('into the root when no parent is given'), which is parameter behavior rather than tool-selection guidance. There is no statement of when to use this versus move_bulk or any other move/rename tool.

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