Move Library items

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

Annotations already declare mutation (readOnlyHint=false), idempotency, non-destructiveness and an open world, so the safety profile is covered. The description adds the meaningful semantic that null folderId removes items from any folder, but says nothing about partial failure across an assetIds array or what the call returns. Adds some value but not rich behavioral context.

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 compact sentence with the action front-loaded and the non-obvious null case appended. Every clause earns its place and nothing is padded.

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?

For a two-parameter mutation tool with no output schema, the description covers the destructive-direction semantics of folderId but omits bulk-move behavior for assetIds, error handling when a folder is missing, and what the caller gets back. Annotations carry the safety profile, so this is adequate but thin.

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 carries the burden. It usefully clarifies folderId semantics (null = out of any folder), which the schema does not express, but assetIds and its array/bulk behavior are left entirely to the schema.

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?

States a specific verb and resource ('Move Library assets') with the destination scope ('into a folder'). It is clearly distinguishable from axcel_library_delete and axcel_library_save_job in the sibling list, but it never names or contrasts against those siblings explicitly.

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 when-to-use guidance, no prerequisites (e.g. folder must exist), and no mention of alternatives such as axcel_library_save_job or axcel_folder_list for locating a target folder. The only usage hint is the parenthetical about passing null.

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