Rename Collection

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

Annotations already declare readOnlyHint=false, openWorldHint=false, and destructiveHint=false, so the agent knows this is a mutating but non-destructive operation. The description adds the key behavioral constraint that the parent is preserved, which is useful. However, it doesn't disclose what happens if the new_name conflicts with an existing sibling collection, or whether the operation is reversible. With annotations covering the basic safety profile, a 3 is appropriate.

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?

Two sentences with zero waste. The core action is front-loaded, and the library targeting rule is stated compactly. Every sentence earns its place.

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 essential context: what the tool does, the parent-preservation guarantee, and the library targeting rule. It doesn't mention edge cases like duplicate names or invalid collection_id, but the output schema and annotations cover the basic contract. The description is complete enough for an agent to call this tool correctly in most cases.

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 for the schema's lack of parameter documentation. The description does explain the library_id/library_type pairing and the default behavior, which adds meaning beyond the raw schema. However, it doesn't explain collection_id or new_name semantics beyond what their names imply. The description partially compensates but leaves some parameter meaning to inference.

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: 'Rename a Zotero collection without changing its parent.' This clearly distinguishes it from sibling tools like delete_collection and move_collection. It could be slightly more explicit about the effect on the collection's position, but the core purpose is clear.

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 this tool: renaming a collection while preserving its parent. It also gives explicit guidance on library targeting: 'Pass both library_id and library_type to target another library; omit both to use the configured default.' It doesn't explicitly name alternatives, but the sibling list and the 'without changing its parent' phrasing imply the distinction from move_collection.

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