add_to_collection

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

With no annotations provided, the description holds the full burden of disclosure. It does reveal an important behavioral trait: duplicates are silently ignored. Yet it omits other potentially relevant behaviors like handling of invalid IDs, permission requirements, or return values, leaving gaps in transparency.

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, well-structured sentence that immediately conveys the core action and a key behavioral detail. It is appropriately sized with no wasted words.

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 add operation, the description covers the essential purpose and a notable behavior (duplicate handling). The schema covers parameter semantics, and no output schema is expected. However, it could mention side effects or error conditions for edge cases like non-existent collection IDs, so it is not fully complete.

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 100%, with both parameters clearly described in the schema. The description does not add extra meaning beyond the schema, so the baseline score of 3 is appropriate.

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 ('Add') and resource ('bookmarks to an existing Collection'), clearly distinguishing it from sibling tools like create_collection and remove_from_collection. The inclusion of 'existing' clarifies it operates on pre-created collections.

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 implies the tool is for adding bookmarks to a collection that already exists, which provides some usage context. However, it does not explicitly state when to prefer this over alternatives or mention exclusion criteria, such as not using it for creating collections.

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