Rename Tag

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

Annotations already indicate a non-read-only, non-destructive operation. The description adds the library-wide scope ('across all items') but does not disclose potential side effects like merging if new_name already exists, or whether the tag must exist beforehand. This is a partial improvement over annotations.

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: one purpose sentence followed by a two-item Args list. No fluff or redundant detail. The structure front-loads the core function.

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?

Given the low complexity (2 required string params) and presence of an output schema and annotations, the description is mostly sufficient. However, it omits important edge-case behavior such as what happens if old_name is not found or if new_name already exists. The instruction to 'rename a tag across all items' is clear, but the consequences of tag name collisions are not addressed.

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?

With schema description coverage at 0%, the description provides basic definitions for both parameters ('The current tag name' and 'The new tag name to replace it with'). These clarify directionality but add little beyond what the parameter names and titles already imply.

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') and resource ('tag') with a clear scope ('across all items in the Zotero library'), which distinguishes it from sibling tools like delete_tags or add_tags. The action and target are unmistakable.

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?

No guidance is provided on when to use this tool versus alternatives such as delete_tags + add_tags or set_tag_color. There are no exclusions, prerequisites, or contextual hints about when renaming is preferable.

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