queue_papers

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

Despite no annotations, the description fully discloses key behaviors: non-destructive addition, duplicate avoidance, optional collection creation on demand, and reporting of unresolvable papers. All behavioral traits are covered.

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 (five sentences), front-loaded with the main purpose, and efficiently provides all necessary details without redundancy. Every sentence adds value.

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 tool's complexity (multiple input types, optional collections, error handling), the description is complete. It covers all aspects an agent needs to know: input, behavior, edge cases, and interaction instructions.

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 0% schema description coverage, the description compensates well by explaining that 'refs' accepts various identifiers and that 'collections' is optional for filing papers, including guidance to use list_collections. Adds significant meaning beyond the raw 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 clearly states the tool adds papers to the Zotero Reading Queue without sending them. It specifies accepted input types and distinguishes from siblings by mentioning it does not send, contrasting with send_papers.

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?

Provides explicit guidance on accepted inputs (arXiv ids, DOIs, URLs, titles), duplicate handling, optional collections, and error reporting. Instructs to check list_collections when placement is unclear, but does not explicitly state when not to use or compare to alternatives.

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