workflow_list_papers

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

Without annotations, the description carries full weight and delivers: it explains the optional cross-check, the performance impact of check_notes ('Slower when True'), and the precedence rule ('collection takes precedence over tag'). It also discloses the default limit and the return format including note_status. No contradictions.

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 well-structured with a concise opening sentence, a usage line, and clearly labeled Args/Returns sections. Every sentence adds value; no redundancy or fluff.

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 (interaction with Zotero and Obsidian, 4 parameters, no output schema), the description covers the return format and parameter behavior well. However, it does not mention prerequisites (e.g., API keys) or error handling, which could be useful for completeness. Still, it is largely adequate.

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 the description must compensate. It does so thoroughly: each parameter is explained with examples (e.g., '待读' or '#待读'), default values, precedence rules, and the effect of check_notes. This adds substantial meaning beyond the bare 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 starts with a clear verb-resource pair: 'List papers from Zotero'. It specifies filtering by tag or collection, and an optional cross-check with Obsidian. This distinguishes it from sibling tools like workflow_get_paper (single paper retrieval) and workflow_sync_highlights (highlight syncing).

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 usage: 'Use this to build a reading queue or to identify papers that still need to be processed.' This provides clear context. It does not, however, mention when not to use it or compare directly with siblings, but the guidance is sufficient.

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