update_collection

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

Annotations already communicate the mutation safely: readOnlyHint=false, destructiveHint=false, idempotentHint=false. The description adds a useful scope constraint, 'without artwork changes,' but does not disclose whether updates are partial/merge semantics, whether rom_ids replaces or modifies membership, or whether null values clear fields. These are meaningful behavioral gaps.

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 front-loaded sentence with no filler. Every word adds scope and purpose, making it easy for an agent to parse quickly.

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 mutation tool with five parameters and no schema-level descriptions, the description is too thin. It omits update semantics, membership replacement behavior, and how this relates to the add/remove-roms sibling tools. The existence of an output schema reduces the need to document return values, but the missing usage and semantics are still significant.

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, but it only gestures at 'metadata/membership.' It does not explain what collection_id targets, how rom_ids behaves, or whether omitted versus null parameters differ. The parameter names carry most of the meaning, leaving important semantics undocumented.

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 begins with a specific verb and resource, 'update collection', and narrows the scope to 'metadata/membership without artwork changes.' This clearly distinguishes it from rom-focused tools and create/delete collection operations, though it does not explicitly contrast with update_smart_collection.

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 about when to use update_collection versus sibling tools like add_roms_to_collection, remove_roms_from_collection, or update_smart_collection. The phrase 'without artwork changes' is a scope restriction, not a selection criterion.

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