edit_collection_instance

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It names the core operations (move and/or rate) but does not disclose side effects, whether rating overwrites existing ratings, whether moving removes from the current folder, or any required permissions.

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 a single front-loaded sentence with no redundant wording. It earns its place by naming the exact scope and actions, though its brevity leaves substantial information to be supplied by schemas or additional context.

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?

This is a mutation tool with no annotations, no output schema, and 6 parameters, yet the description provides only the core action. An agent is left without enough context about parameter relationships, side effects, or success/failure behavior to invoke 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 for the 6 parameters. It weakly maps actions to parameters ('move' implies currentFolderId/newFolderId, 'rate' implies rating), but it does not explain the role of username, required fields, or optionality.

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 and/or rate one exact collection copy.' It clearly conveys this acts on an existing single collection instance, which differentiates it from siblings like add_to_collection and remove_collection_instance despite not naming them.

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 explicit guidance on when to use this tool versus alternatives. The description implies it is for editing an existing collection copy, but it does not mention exclusions, prerequisites, or compare with sibling tools like remove_collection_instance or add_to_collection.

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