manage_collection

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

With no annotations, the description carries the full transparency burden. It discloses one meaningful side effect: 'move 会把对象从其它集合移出'. However, it does not explain the behavior of delete, link, unlink, or rename, nor whether actions are destructive, reversible, or require special conditions.

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 very short and front-loaded: it states the resource, lists the actions, and adds one key behavioral note. Every sentence earns its place, though the brevity contributes to the overall lack of detail.

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 multi-action tool with 5 parameters, no annotations, and no output schema, the description is incomplete. It omits parameter roles, action-specific requirements, return behavior, and edge cases, so an agent would likely need additional probing before calling it confidently.

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 must compensate. It adds useful meaning for the action parameter by listing valid values, but it does not explain name, parent, objects, or new_name, nor which parameters each action requires. This leaves most parameters underspecified.

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 identifies a specific resource ('collection') and an operation set (create/delete/move/link/unlink/rename), so an agent can tell it is a collection-management tool. It is somewhat generic in using '管理' but the action list gives concrete scope and separates it from object-level siblings like delete_object or rename_object.

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?

No explicit when-to-use guidance, no exclusion criteria, and no alternative tools are named. The action list implies usage for collection operations, but it does not clarify when to choose this over related object-management tools or what preconditions/context apply.

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