import_bibtex_library

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

No annotations are provided, so the description must fully disclose behavior. It indicates a write operation ('import') but does not detail side effects (e.g., duplicate handling, overwrite policy), authentication requirements, error conditions, or return value structure. This lack of detail reduces transparency for a mutation tool.

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 concise, with two sentences plus an argument description. It front-loads the purpose. However, it could be slightly more structured (e.g., separate sections for usage and args). Still, it avoids verbosity and is efficient.

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 parameter tool, the description covers the main purpose and usage scenario. However, with no annotations and an existing output schema (which it does not reference), it lacks information about expected output, error handling, and prerequisites (e.g., file existence, format). It is adequate but not thorough.

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?

The input schema has 0% description coverage for the parameter, but the description adds meaningful context: 'Full path to the .bib file (e.g. from Mendeley export).' This clarifies that a full path is expected and provides an example usage, which goes beyond the schema's mere name 'Bibtex Path'.

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 states the tool's action ('Import papers from a BibTeX file') and the target ('into literature_metadata'). The verb is specific ('Import') and the resource is clearly identified. Among sibling tools, none duplicate this function, so it distinguishes well.

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 provides a concrete use case: 'Use this for Mendeley users: export your library from Mendeley as BibTeX, then point this tool at the file.' This guides when to use it. However, it does not mention alternatives or explicitly state when not to use it, so it is not a full 5.

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