add_to_collection

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds only the mild ownership constraint ('the user's collections'); it says nothing about duplicate handling, the 100-image cap, partial-failure behavior, or permission requirements for a non-idempotent mutation. With annotations carrying most of the burden this is a small but real gap.

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?

It is a single front-loaded sentence with no filler, so it is not padded. However, brevity here comes at the cost of under-specification rather than efficiency, so it earns only a middling score.

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?

An output schema exists, so return values need no explanation, but this is a non-idempotent write tool with two required, entirely undocumented parameters and a batching limit. The description omits what happens to images already in the collection and whether the operation is all-or-nothing, leaving the agent under-informed for a mutation.

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 and it does not. Neither collection_id nor image_ids is explained, and the important limits encoded in the schema (image_ids minItems=1, maxItems=100) are never surfaced in prose. The names are largely self-explanatory, which keeps this above a 1.

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 ('Add images to ... collections'), which lets an agent separate it from get_collection, create_collection, and list_collections. It does not explicitly name a sibling, but the mutation-versus-read distinction is implied by 'Add'.

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 guidance on when to use this tool versus create_collection or get_collection, no mention of prerequisites (does the collection need to pre-exist?), and no exclusions. The only implied usage is that an existing collection is targeted via 'one of the user's collections'.

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