move_views

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

No annotations exist, so the description must fully disclose behavioral traits. It reveals that the tool moves views (implying mutation) and that dry_run shows intended changes without execution. However, it does not disclose whether views are copied or cut, whether original views are deleted, any side effects, permissions required, or the backup behavior despite a backup parameter existing.

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 and concise: four short lines covering the action and key parameters. No redundant or irrelevant sentences. Every element adds value.

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 absence of annotations and output schema, the description should fully equip an agent to invoke the tool. It fails to define the 'xml' parameter and does not clarify the backup behavior. Essential context like file scope and move semantics is missing, leaving the agent underinformed.

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?

With 0% schema description coverage, the description must compensate. It explains from_folder, to_folder, names, and dry_run adequately. However, it omits explanations for the 'xml' parameter (likely the file identifier) and the 'backup' parameter, leaving ambiguity for critical fields.

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 clearly states the action (переместить 'move'), the resource (view), and the constraint (по точным именам между папками одного файла – 'by exact names between folders of one file'). It distinguishes from sibling tools that handle deduplication, merging, or sorting, as this is specifically about moving views between folders within a file.

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 does not indicate when to use this tool versus alternatives like rename_folder, sort_viewpoints, or sync_lists. No prerequisites or exclusions are mentioned. The only usage hint is the dry_run parameter, but it lacks explicit when-to-use and when-not-to-use guidance.

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