Add Item to Collection

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

With no annotations, the description must carry the transparency burden. It does add useful behavioral context: an item can belong to multiple collections (additive action) and the need to list collections implies the collection must already exist. However, it doesn't disclose what happens when an item is already in the collection, whether the item must exist, or potential failure modes.

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?

Three short sentences, all informative and front-loaded with the purpose. No filler or redundancy.

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 simple two-parameter mutation tool with no output schema and no annotations, the description covers the core operation, a prerequisite, and an important semantic detail. It lacks edge-case behavior like duplicate handling, but the tool is simple enough that the description is adequate for an agent to call it correctly.

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?

The schema fully describes itemKey and collectionKey as strings, so baseline is 3. The description adds value by explaining that collectionKey can be obtained via list_collections and that an item can belong to multiple collections, which gives semantic meaning to the parameters beyond 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?

The description uses a specific verb and resource: 'Add an item to a collection.' It clarifies that a collection is a folder and notes that an item can belong to multiple collections, which distinguishes it from tools like create_collection or add_tags_to_item.

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 description provides clear context for using the tool and tells the agent to use list_collections to obtain valid collection keys. It doesn't explicitly state when not to use the tool or name alternatives, but the prerequisite guidance is helpful.

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