zotero_set_item_parent

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

With no annotations, the description carries the behavioral burden. It clearly discloses that the tool mutates parentage, that passing null clears the parent, and that Zotero validates allowed relationships. This goes beyond a minimal 'set parent' statement, though it does not detail response or error 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?

The description is compact and front-loaded with the core action. Each sentence contributes useful information, with no repetition or filler.

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 two-parameter tool with an output schema, the description covers the essential semantics and the tool's validation behavior. It is sufficient for an agent to invoke correctly, though it could mention key format or specific relationship constraints.

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 explains parent_key meaningfully: a string key assigns/changes the parent, null makes the item top-level. item_key is less detailed but its purpose is clear from the tool context.

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 action and resource: 'Set or clear the parent of a Zotero item.' It clearly distinguishes itself from related siblings like zotero_set_item_collections or zotero_update_item by focusing solely on the parent-child relationship.

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 implies when to use the tool—when you need to assign, change, or clear an item's parent—but it does not explicitly discuss alternatives or when not to use this tool. The guidance is mostly parameter-level rather than decision-level.

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