Rename Tag

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

The annotations include readOnlyHint=false, destructiveHint=false, and openWorldHint=false, which require the description to clarify mutation effects. The description states it renames 'across all items', indicating a non-destructive but broad change. However, it does not disclose whether the rename is reversible, whether conflicts with existing tags are handled, or the effect on other metadata. This is a moderate gap given the tool's mutating nature.

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 concise, with a one-sentence purpose statement and a brief Args list. It front-loads the main action and scope, then provides parameter details in a structured way. No redundant information; every sentence serves a purpose.

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?

The tool is relatively simple with only four parameters, and the description covers the main action, parameter meanings, and library targeting behavior. It doesn't mention return values, but there is an output schema that likely fills that gap. It could add a note about error handling or idempotency, but overall it is adequate for an agent to invoke 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 description coverage is 0%, so the description must compensate for the schema's lack of parameter descriptions. The description explains 'old_name' and 'new_name' meanings in the Args section, adding clarity beyond the schema's simple type definitions. However, it doesn't elaborate on library_id and library_type beyond the usage note, but those are optional and their roles are partially clear from their names and the note.

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 clearly states the action ('Rename') and the resource ('a tag across all items in the Zotero library'), which is specific and distinguishes it from sibling tools like delete_tags or add_tags. It also explains the function's scope (across all items), which is crucial for an agent to understand its reach.

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 explicit usage conditions: 'Pass both library_id and library_type to target another library; omit both to use the configured default.' This is clear when-to-use guidance that helps the agent decide how to call the tool. It also implicitly differentiates from other tag tools by focusing on renaming, which is unique among siblings.

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