zotero_set_item_parent

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

With no annotations provided, the description carries the full behavioral burden and does meaningful work: it discloses that the operation is a mutation, that null clears the relationship, and that Zotero validates whether the parent-child relationship is allowed. It stops short of describing failure behavior, side effects on existing child items, or reversibility, but the core behavioral traits are honestly surfaced.

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 sentences, each earning its place: the core operation, the parameter semantics for both modes, and a relevant validation note. The primary verb and resource are front-loaded, and there is zero filler or repetition of schema content.

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 low-complexity tool (two flat scalar parameters, no enums, output schema already present), the description covers the operation, the parameter behavior, and the validation constraint—enough for an agent to invoke it correctly. The only omissions are minor: no mention of prerequisites (the item and parent must exist) and no disclosure of cascading effects when reparenting an item that has its own children.

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 for the critical parameter: parent_key's dual meaning (key to assign/change, null to make top-level) is explicitly documented. item_key's role as the item being reparented is only implied by the first sentence rather than stated, which is the main gap.

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 opens with a specific verb+resource combination ('Set or clear the parent of a Zotero item') that precisely defines the operation. It also explains both modes—assigning/changing a parent or clearing it to top-level—making the tool's scope unambiguous and naturally distinct from siblings like zotero_get_item_children or 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 how-to instructions for the two operational modes ('Pass a parent item key... or null to make the item top-level'), so usage context is implied rather than absent. However, it never explicitly states when to prefer this tool over alternatives such as zotero_update_item or zotero_set_item_collections, and names no exclusions.

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