Rename Collection

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

The annotations are minimal (readOnlyHint false, destructiveHint false), so the description carries some burden. It adds one useful behavioral note ('without changing its parent'), but does not mention any other side effects, uniqueness constraints, or permission requirements. This is adequate but not rich.

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 a single, focused sentence that communicates the essential purpose and the key constraint without any waste. It is front-loaded and easy to parse.

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 rename operation with an output schema present, the description covers the core function and the critical distinction from sibling tools. It does not need to explain return values. It could include more about edge cases, but the tool's low complexity makes this sufficiently 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% and the description adds no explanation of the parameters (collection_id, new_name). Although the parameter names and titles are self-explanatory, the description fails to compensate for the lack of schema descriptions, leaving the agent to infer parameter semantics.

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 uses a specific verb 'Rename' with the resource 'Zotero collection' and adds a key scoping detail 'without changing its parent,' which clearly distinguishes this from moving the collection. It directly states the tool's function.

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 provides clear context for when to use the tool: renaming a collection while preserving its hierarchical position. The phrase 'without changing its parent' implies a contrast with move_collection, though it does not explicitly name the alternative.

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