scite_enrich_search

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

Discloses use of free public endpoints (transient failures possible), items without DOI get no Scite fields, returns Zotero results even if Scite fails, and no API key required. Covers all important behavioral traits.

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 fairly long but well-structured, front-loading purpose and usage, then parameters and caveats. Every sentence adds value, though a bit verbose.

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 2 params, no enums, and existence of output schema, the description covers all necessary aspects: return format (markdown like zotero_search_items with extra fields), error handling, scope, and dependencies. No gaps.

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 coverage, the description fully explains both parameters: query semantics (substring, 'Author Year' best, extra words narrow) and limit (max results, default 10). Adds meaning 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 clearly states it searches Zotero and enriches with Scite citation tallies and notices, and distinguishes from siblings like scite_enrich_item and zotero_search_items.

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?

Explicitly tells when to use this tool vs alternatives: use instead of scite_enrich_item for batched requests, use zotero_search_items for plain search, and use scite_check_retractions for retraction-only scans. Also mentions scope and library switching.

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