Zotero Set Item Parent

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

With no annotations present, the description carries the behavioral burden. It discloses that this is a mutating operation, that null makes the item top-level, and that Zotero validates allowed parent-child relationships. However, it does not mention write-authorization requirements or side effects on child items, which are relevant for a mutation tool.

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?

Three short sentences front-load the core purpose, immediately give the null behavior, and add the validation caveat. There is no filler or restatement of schema information.

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?

The tool is simple, has an output schema, and the description covers the main invocation semantics and validation behavior. The only notable gaps are the implicit role of item_key and the absence of write-authorization notes, but for a low-complexity tool this is close to 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 0%, so the description must compensate. It clearly explains parent_key semantics (parent key or null for top-level), but item_key is only implied as the item being modified and is never explicitly described. This partial parameter coverage warrants a 3.

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: 'Set or clear the parent of a Zotero item.' It also clarifies the null case (make top-level), which distinguishes this from read-only sibling tools like zotero_get_item_children and from collection operations like zotero_set_item_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 gives clear usage context: passing a parent key assigns/changes the parent, and passing null clears it. It stops short of a 5 because it does not explicitly mention alternatives or when not to use this tool, but the usage context is unambiguous.

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