import_bibtex_library

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

No annotations are provided, so the description carries full burden. It discloses the tool performs a write operation (import) but does not mention side effects (e.g., deduplication, overwrites, validation) or system dependencies.

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 with two sentences and a parameter hint, front-loading the core purpose. No fluff or redundant information.

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 low complexity (one parameter, output schema present), the description covers the essential input semantics. It does not address potential issues like missing files or duplicate entries, but the output schema is assumed to document the return values.

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 description coverage is 0%. The description adds 'Full path to the .bib file (e.g. from Mendeley export)' which clarifies the parameter beyond the schema's type string but remains minimal. More detail on file accessibility or format would improve the score.

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 imports papers from a BibTeX file into literature_metadata, using a specific verb and resource. It distinguishes itself from sibling tools like scan_literature or mine_references by being the only tool focused on BibTeX imports.

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 explicitly advises Mendeley users to export their library as BibTeX, providing clear context when to use this tool. It lacks explicit when-not guidance or alternative tool references but is still actionable.

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