remove_collection_instance

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

With no annotations, the description carries the disclosure burden. 'One exact copy' adds a meaningful behavioral trait: only the specific identified instance is removed, not every copy of a release. 'Remove' also conveys destructiveness. However, it does not disclose irreversibility, permission requirements, or what happens on errors, so the disclosure is partial.

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 seven-word sentence with no filler; 'exact' earns its place by adding precision. It is well-structured and front-loaded, but the conciseness comes at the expense of operational detail, so it is not perfect.

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 destructive tool with no annotations, no output schema, and zero parameter documentation, this description is too thin. It does not clarify how folderId and instanceId relate to the removal, and it refers to 'a collection' while the schema requires a specific folderId. An agent is left guessing about the invocation mechanics.

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%, and the description does not explain folderId, username, releaseId, or instanceId. The phrase 'exact copy' hints at why instanceId matters, but it does not tell an agent how to populate required parameters or handle the optional username. The description fails to compensate for the absent schema documentation.

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 the verb 'Remove', the resource ('a collection' instance/copy), and scopes the operation to 'one exact copy,' which distinguishes it from edit_collection_instance and remove_from_wantlist at a high level. It could be stronger by explicitly naming a sibling or tying 'copy' to instanceId, but the core action is unambiguous.

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 guidance is given on when to use this tool versus edit_collection_instance, add_to_collection, or remove_from_wantlist. There are no conditions, prerequisites, or exclusions. The only contextual signal is the sibling list itself, which the description does not engage with.

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