Export BibTeX

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

The description discloses that the tool returns raw BibTeX text ready to paste into a .bib file and that the output is generated by Mendeley. However, it does not explain how the limit parameter affects folder exports, and the claim of exporting 'all documents in a folder' sits uneasily with the default limit of 50.

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 compact and front-loaded: the action and the critical one-of rule appear immediately. Every sentence adds useful information, with no filler or repetition.

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?

The output schema covers return structure, but the description omits the behavior of the limit parameter and appears to contradict it by saying 'all documents' when the default limit is 50. An agent could under-export a large folder without realizing it, and the one-of constraint is not enforced by the schema, so the description must fully explain the boundary conditions but does not.

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 description adds meaningful exclusive-or semantics for document_id and folder_id, which the schema lacks since no parameters are required. However, schema description coverage is 0%, and the limit parameter is not explained at all, leaving one of three parameters semantically opaque.

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 identifies the action (export), the resource (BibTeX), and the scope (one document or all documents in a folder). It also states the output format, which distinguishes it from the sibling tools that search, fetch, or manage Mendeley records.

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 an explicit, actionable usage rule: 'Provide exactly one of document_id or folder_id.' It does not explicitly discuss when to prefer this tool over siblings, but the tool's unique export purpose makes that context reasonably clear.

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