EndNote Library Reader

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

With no annotations provided, the description carries full burden and successfully discloses critical failure modes ('operation will fail due to file locking') and conditional behavior ('No effect if backup mode is off'). Could explicitly state whether this is destructive/idempotent, but covers essential safety constraints.

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?

Three sentences with zero waste: first establishes action and availability, second clarifies negative condition, third provides critical prerequisite. Front-loaded structure with essential safety information included.

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 narrow scope (0 parameters, simple operation) and presence of output schema, the description adequately covers operational constraints. Could explicitly characterize the 'refresh' operation type (write/update), but prerequisites and failure modes are well-documented.

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?

Zero-parameter tool with empty schema (100% coverage). Per guidelines, 0 params = baseline 4. The description appropriately requires no parameter explanation.

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 uses specific verb 'refresh' with explicit resource '.enl.backup file', clearly distinguishing it from sibling paper-management tools (list_papers, read_paper, search_papers). It additionally scopes availability with 'only available when backup mode is enabled'.

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 prerequisites ('You must close EndNote before refreshing') and conditional usage ('only available when backup mode is enabled', 'No effect if backup mode off'). Lacks explicit alternative tool recommendations, though siblings serve entirely different purposes.

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