add_entry

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

No annotations are provided, so the description carries the full burden—and it excels. It discloses the internal mechanism (jabref --importBibtex), the side effect (entry added to the currently open library), duplicate detection behavior, and the important fact that the .bib file is never modified by the server. It also describes the runtime prerequisite clearly.

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 longer than average but every sentence contributes meaning: purpose, mechanism, side effects, prerequisites, and parameter explanation. It is front-loaded with the core purpose and uses bullets for readability. No obvious filler, though it could be slightly tightened without losing value.

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 complexity, no annotations, and 0% schema coverage, the description is quite complete: it explains the primary parameter format, prerequisites, behavior, and return value ('Returns the canonical BibTeX that was sent to JabRef'). It does not cover error cases (e.g., what happens if JabRef isn't running) or timeout defaults, but it provides enough for an agent to invoke it correctly in normal conditions.

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%, so the description must compensate for the bare schema. It does: bibtex is explained as 'a complete BibTeX entry' with a concrete example, and timeout is described as 'optional override of the import timeout in seconds,' adding units and purpose. This is sufficient for correct invocation, though it doesn't mention the default timeout value or edge-case behavior.

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 opening sentence states a specific action and resource: 'Add a new entry to the JabRef library.' It further emphasizes this is the 'ONLY supported way of adding entries,' which clearly distinguishes it from the read-oriented sibling tools like list_entries, get_entry, and search.

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 tells the agent when to use this tool: whenever an entry needs to be added, and explicitly frames it as the only supported method for adding entries. It also lists concrete prerequisites (JabRef running, remote operation port enabled, Preferences -> Network), which is essential operational guidance, though it does not spell out when-not-to-use or contrast with specific alternatives beyond the 'ONLY supported way' phrasing.

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