zotero_find_related_papers

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

No annotations provided, so description carries full burden. It explains the OpenAlex source, flagging of existing items, sorting behavior, and requirements. Does not mention rate limits or error cases but covers key behaviors well.

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?

Well-structured: purpose first, then usage, then parameter details, then example. Approximately 120 words, no unnecessary content.

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 an output schema available, the description adequately covers purpose, usage, parameters, and behavior. Mentions flagging for existing items and alternative tool. Complete for an agent to use correctly.

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%, but description fully explains identifier (Zotero key or DOI/DOI-URL), direction (enum with examples), and limit (default, max, and per direction). Adds sorting details beyond 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 discovers related papers via citation graph using OpenAlex, distinguishes from siblings by mentioning the specific use case of literature review and referencing zotero_add_by_doi.

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 clear context for when to use (expand literature review) and prerequisite (resolvable DOI in OpenAlex). Mentions spot gaps and alternative tool. Lacks explicit when-not but sufficient context.

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