zotero_rename_tag

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It discloses the key behaviors: renaming on every item and merging into existing tags. However, it does not mention failure conditions, idempotency, or the response format. The 'via the web API' phrase is trivial and adds little. While the merge behavior is useful, additional details about side effects would improve transparency.

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?

A single, concise sentence that front-loads the action and scope. Every word earns its place, and the critical merge behavior is included. There is no redundancy or fluff, making it easy to parse quickly.

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?

With no output schema and no annotations, the description must be self-sufficient. It covers the core operation and merge behavior, but it omits the return value, error handling, and edge cases (e.g., nonexistent tag, case sensitivity). For a mutation tool with three parameters, the description is minimal but not severely lacking. It meets the minimum bar but leaves room for more detail.

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 100%, meaning all three parameters (tag, newName, library) are already documented in the schema. The description does not add any parameter-specific meaning beyond what the schema provides. The mention of 'every item' clarifies scope but is not a parameter detail. Baseline of 3 is appropriate given full schema coverage.

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 ('Rename'), a clear resource ('a tag'), and the scope ('on every item that carries it'), plus the merge behavior. This clearly distinguishes it from siblings like zotero_delete_tags and zotero_tag_items, which perform different operations. An agent can confidently identify what this tool does without ambiguity.

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 implies when to use the tool (when a tag needs renaming across all items), but it does not explicitly mention alternatives or situations where another tool would be more appropriate. No exclusions or comparisons with sibling tools are given, so guidance is inferred rather than stated. This is acceptable but not explicit.

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