zotero_manage_collections

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

No annotations provided, so description carries full burden. It states it adds/removes items but does not disclose side effects (e.g., overwriting?), permissions needed, or behavior when item already in collection. Lacks behavioral depth beyond the basic operation.

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, front-loaded with the action, then concise parameter guidance. No filler words; every sentence adds necessary clarification.

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?

Output schema exists (not shown), so description need not explain return values. It covers purpose, parameter semantics, and links to sibling tools. For a collection management tool with moderate complexity, it provides sufficient context to use correctly.

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 coverage is 0%, so description compensates by clarifying that item_keys, add_to, remove_from must be arrays, and gives an example format. This adds significant meaning beyond the anyOf schema definitions.

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?

Description starts with 'Add or remove one or more items from collections', which is a specific verb+resource. It clearly distinguishes from sibling tools like zotero_create_collection and zotero_delete_collection.

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?

Provides guidance on when to use this tool (managing items in collections) and gives parameter usage instructions (arrays vs single strings). Does not explicitly say when not to use, but implies context by referencing sibling tools for finding keys.

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