Update Item Metadata

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

With annotations only providing readOnlyHint=false and destructiveHint=false, the description adds meaningful behavioral context: certain fields are immutable, and creators are 'replaced' rather than merged. This goes beyond the schema and annotations, though it does not detail partial update semantics or response behavior.

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?

Two brief sentences carry all essential information: the action and the constraints. No filler or redundant wording; the description is front-loaded and easy to scan.

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?

Given the 3 parameters and nested objects, the description is reasonably helpful but incomplete. It clarifies what can and cannot be changed, but does not specify how to construct the updates object or creator entries, and the output schema is not shown. An agent might still need to infer allowed metadata keys.

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%, and the description partially compensates: it explains that 'updates' holds bibliographic fields and 'creators' replaces creators. However, it does not explain the format of item_key, allowed field names, or the creator object structure, leaving some ambiguity.

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 clearly states the action ('Update selected bibliographic fields') and the optional scope ('optionally replace creators'), making the tool's purpose immediately obvious. It is distinct from sibling tools like delete_item, trash_item, or update_annotation by focusing on bibliographic metadata of an 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 gives implied usage context: use for bibliographic field updates and optional creator replacement. It also explicitly lists immutable fields that cannot be changed through this tool, which is a form of when-not guidance, but it does not name alternative tools for those cases (e.g., add_to_collection, trash_item).

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