EndNote Library Reader

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

With no annotations provided, the description carries the full disclosure burden. It successfully communicates fuzzy matching behavior and case-insensitivity, but omits operational details like error handling (not-found scenarios), idempotency, or whether the PDF is downloaded/cached.

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?

Four information-dense sentences with zero redundancy. The structure flows logically from purpose → usage → parameters → output → example, with critical information front-loaded. Every sentence adds value beyond the structured fields.

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 single-parameter input and presence of an output schema (not shown but referenced), the description appropriately details the return fields and fuzzy search semantics. Minor deduction for not explicitly contrasting with search_papers for keyword queries.

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?

Despite 0% schema description coverage, the description fully compensates by detailing the 'title' parameter's type, constraints ('case-insensitive, fuzzy match'), and provides a concrete usage example ('read_paper('Knowledge Distillation Review')'), leaving no ambiguity.

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 opens with a precise action ('Find a paper') and clearly specifies the retrieval method ('fuzzy title') and return scope ('metadata and PDF full text'). This distinguishes it from siblings like search_papers (likely keyword-based) and list_papers (likely enumeration).

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 when-to-use guidance ('Use when the user needs the full content and bibliographic info'), establishing clear intent. However, it lacks explicit when-not-to-use guidance or direct references to sibling alternatives like search_papers.

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