file_papers

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

With no annotations, the description carries full burden and discloses key traits: collection creation on demand (only if papers match), items stay in queue, delivery state unaffected, and matching method. Missing details on error handling or authentication, but overall transparent.

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?

Six sentences with no wasted words. The main purpose is front-loaded, and every sentence adds essential information (prerequisite, alternative, side effects, matching behavior). Very concise.

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 two-parameter tool and presence of an output schema, the description covers prerequisites, side effects, matching, and edge cases (empty collection not created). It is nearly complete; the output structure is covered by the output schema.

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 coverage is 0%, so description must add meaning. It explains that 'refs' uses exact matching (arXiv id, DOI, URL, title) and implies 'collection' is a name. The description adds value beyond the schema, though collection format is not detailed.

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 verb 'file' and resource 'already-queued papers into a Zotero collection', and it distinguishes from siblings like queue_papers (which queues) and unfile_papers (implied inverse). The matching method and prerequisite are explicit.

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 explicitly states when to use (only for papers already in the queue), when not to (for fresh papers, use queue_papers), and provides an alternative (pass collections to queue_papers). Also covers the condition that collection creation only occurs if papers match.

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