add_to_collection

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

With no annotations, the description carries the full burden. It discloses the mutation ('Add'), the scope ('one copy'), and the return value ('its instance ID'). It does not mention duplicate behavior, default folder handling, authentication, or side effects, but it does provide the core behavioral outcome.

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, focused sentence that front-loads the action and states the result. There is no wasted wording.

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?

The tool has no annotations and no output schema, and the description omits important details such as the username parameter, default folder behavior, duplicate copy semantics, and authentication context. An agent would need additional inference to call it confidently in all cases.

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 implicitly maps releaseId and folderId via 'release' and 'collection folder', but it does not explain the username parameter, the folderId default, or why these are needed.

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: adding one copy of a release to a collection folder and returning its instance ID. This clearly distinguishes it from sibling tools like add_to_wantlist or remove_collection_instance.

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 usage context is implied: use when adding a release copy to a collection folder. However, it does not explicitly say when to prefer this over alternatives, such as add_to_wantlist, or mention any exclusions.

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