read_fileRetrieves a text file from a Filen cloud drive and returns its UTF-8 content, rejecting non-regular files or files over 5 MB.
Read a text file from the Filen cloud and return its UTF-8 content. Refuses files that are not regular files or larger than 5 MB (use download_file for those).
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Absolute cloud path of the file to read |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
While annotations provide safety hints, the description adds critical operational behavior: the file must be a 'regular file' and cannot exceed 5 MB. These constraints prevent misuse and clarify the tool's functional limits beyond the schema.
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 definition is highly concise and efficient. It front-loads the core functionality and immediately follows with the necessary constraints and routing logic.
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?
Despite having no output schema, the description is fully complete. It covers the function, the expected content type, the hard limits (5MB, file type), and the correct tool to use for overflow, leaving no major gaps for an agent to resolve.
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?
Given that the input schema coverage is 100%, the description does not need to define the 'path' parameter. However, it adds valuable semantic information regarding the output format (UTF-8 content) and the content type expectation (text file).
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 states the primary function: reading a text file and returning its UTF-8 content. Crucially, it distinguishes itself from siblings like download_file by specifying its size and type limits.
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?
It provides explicit usage guidelines by defining failure conditions (non-regular file, > 5MB) and directs the user to an alternative tool (download_file) when those conditions are met, making decision logic straightforward.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.