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 burden. It successfully discloses pagination behavior (offset/limit mechanics), default values (0 and 10), and detailed return structure ('list of dicts with fields: id, title...'). It could improve by explicitly stating the read-only/safe nature of the operation.

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 optimally structured across four sentences: purpose declaration, parameter explanation, return value documentation, and usage example. Every sentence adds unique value; there is no redundancy with the schema or padding.

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 has 2 simple parameters and an output schema exists, the description is nearly complete. It compensates for the schema's lack of property descriptions and preemptively documents return fields (even though the output schema makes this optional). Minor gap: no mention of relationship to sibling 'search_papers'.

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 (neither property has a description field), the text fully compensates by documenting both parameters: 'offset (int, default 0)' and 'limit (int, default 10)', explaining their joint purpose ('to fetch a page of results'), and providing a concrete example ('list_papers(offset=0, limit=10)').

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 specific verb ('Return') and resource ('references in the EndNote library') and clarifies the scope ('with pagination'). It effectively distinguishes from siblings: 'read_paper' implies fetching content, 'search_papers' implies filtering, while this tool returns the full list with pagination controls.

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 implies usage through the pagination mechanism ('Use offset... and limit... to fetch a page'), suggesting iterative browsing. However, it lacks explicit guidance on when to choose this over 'search_papers' (e.g., no statement like 'use this for unfiltered browsing, use search_papers for keyword filtering').

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