Update Collection Metadata

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

The description adds no behavioral context beyond what annotations already provide. Annotations indicate this is a mutating but non-destructive, idempotent operation; the description merely says 'update' without disclosing partial-update behavior, permission requirements, or side effects. No contradiction exists, but no new information is added.

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 efficient sentence with no filler or unnecessary elaboration. It is concise and immediately front-loaded, though it largely echoes the title.

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 update tool with full schema coverage and annotations covering mutation safety, the description plus schema is minimally viable for constructing a call. However, it is incomplete in routing an agent to this tool over siblings and in explaining the update semantics beyond the parameter list.

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%, so the input schema already documents title, collId, language, and description. The description does not need to explain these, but it also adds no extra semantic detail such as whether unspecified fields remain unchanged.

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: 'Update the metadata for a collection.' This clearly conveys the operation and target. However, it does not distinguish itself from similar sibling tools such as transkribus_coll_modify or transkribus_doc_update_metadata.

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 this tool versus alternatives, no prerequisites, and no exclusions. The description only restates the purpose, leaving an agent to infer selection from the tool name alone despite the large sibling set.

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