Get File Content

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

With no annotations provided, the description carries the full burden and does disclose important behavioral traits: it 'tries' to download, it only handles the first file, and the PDF is only returned 'when Mendeley exposes one'. It does not cover error handling or side effects, but for a read/download operation the key uncertainties are surfaced.

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 two short, front-loaded sentences with no filler. The action, target, return value, and main caveat are all covered efficiently, and every clause contributes meaningful 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?

For a one-parameter tool with no output schema and no annotations, the description gives enough to invoke it correctly and to set expectations about the returned metadata and embedded PDF. Exact return structure and failure behavior are not documented, but the caveats 'try' and 'when Mendeley exposes one' partially cover those gaps.

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%, and the description only indirectly defines document_id by referring to 'a library document or catalog entry'. This gives some context, but it does not specify the ID format, its origin, or how it relates to IDs used by sibling tools, so the compensation for the missing schema descriptions is only partial.

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 a specific action ('try to download') and a specific resource ('first file attached to a library document or catalog entry'), which clearly distinguishes it from siblings like mendeley_get_document or mendeley_get_document_text. It also adds the conditional caveat about whether Mendeley exposes a PDF, making the tool's purpose unambiguous.

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 clearly indicates when to use this tool: when an agent needs the file content of a document's or catalog entry's first attachment. It does not explicitly name alternatives or provide exclusion criteria, but the context is clear enough to guide tool selection without opening other definitions.

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