Metis · Librarian — Import Bibtex Library

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the basic import operation without discussing side effects (e.g., duplication handling, overwrite behavior, validation). A user or AI agent would not know if this action is destructive or idempotent, or if it requires specific file permissions.

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 extremely concise: two sentences for purpose and usage, plus a two-line args section. Every sentence contributes useful information, and there is no redundancy or fluff. The structure is clear and easy to scan.

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?

For a simple one-parameter tool with an output schema, the description is adequate but incomplete. It lacks guidance on error cases (e.g., invalid BibTeX, file not found), expected output format (though output schema exists), and whether the tool validates entries before importing. The description meets minimum viability but misses behavioral and error-handling context.

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%, so the description adds meaning beyond the schema. It describes the sole parameter 'bibtex_path' as 'Full path to the .bib file (e.g. from Mendeley export).' This clarifies that it expects a file path and gives an example. However, it does not specify whether relative paths or remote paths are allowed, nor does it mention file encoding.

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's action ('Import papers from a BibTeX file') and resource ('into literature_metadata'). The verb 'import' and target 'literature_metadata' are specific. Among siblings like other import/search tools, this one uniquely handles BibTeX import, so it is well-distinguished.

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 gives a concrete use case ('Use this for Mendeley users: export your library from Mendeley as BibTeX, then point this tool at the file.'). This provides clear context for when to use it, but it does not explicitly state when not to use it or mention alternatives. Other import tools exist (e.g., import_citations) but are not referenced.

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