get_bibtex

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

Discloses that it resolves various identifier formats and returns BibTeX entry, title, texkey, and resolved ID. No annotations provided, so description carries full burden; covers key behaviors well.

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?

Concise and well-structured with bullet list and Args section. Front-loaded with purpose, no redundant sentences.

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?

Covers input and output well given 1 parameter and output schema exists. Lacks error handling or format details but sufficient for a retrieval tool.

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 description must compensate. Description clearly explains identifier parameter with examples for DOI, arXiv ID, and Inspire ID, adding significant meaning.

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?

Clearly states 'Retrieve the BibTeX citation entry for a paper.' verb and resource are specific. Distinguishes from siblings like get_citations, get_paper_details by focusing on BibTeX format.

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?

Lists accepted identifier formats but no explicit guidance on when to use this vs alternatives. Usage is implied but not explicitly stated.

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