remove_from_queue

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

With no annotations to rely on, the description fully discloses behavioral traits: items filed elsewhere keep their library record, items without other collections move to Trash (restorable ~30 days), trashed items no longer count for duplicate protection, and nothing is permanently deleted from Zotero or the e-reader. This richly supplements the bare schema.

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 efficiently structured with a clear lead sentence followed by bullet-like paragraphs. Every sentence serves a purpose (behavioral details, edge cases, user guidance), but the flow could be tightened slightly (e.g., merging duplicate-handling into a single sentence) without losing clarity.

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?

Despite the simple single-parameter schema, the tool has complex side effects (trashing, collection membership, duplicate protection). The description covers all these scenarios, including behavior on duplicate matches and instructions for user interaction. An output schema exists, so return value explanation is unnecessary.

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?

The input schema only defines 'refs' as an array of strings without descriptions. The tool description compensates by specifying acceptable formats (arXiv id, DOI, URL, exact title) and explains matching behavior, uniqueness constraints, and the need for disambiguation—adding essential semantic value beyond the schema.

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 opens with 'Remove papers from the Zotero Reading Queue by ref or title', a specific verb-resource pair that clearly distinguishes this tool from siblings like list_queue (listing), queue_papers (adding), and send_queue (sending). It leaves no ambiguity about the core 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 a clear context for use (removing items from the queue) and explains behavior on duplicate matches, but it does not explicitly list when this tool should be avoided or name direct alternatives. The guidance within (e.g., 'Relay the choice to the user — never pick for them') adds operational context.

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