Read Nextcloud text file

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

The description adds a behavioral detail (size limit) beyond the readOnlyHint annotation, but nothing else about error handling or return behavior. It is consistent with annotations and adds a small extra context.

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 a single, clear sentence with no fluff, perfectly sized for the tool's simplicity.

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 simplicity of the tool and the existence of an output schema (not shown but indicated), the description adequately covers the core operation. It does not mention distinguishing from binary downloads, but the name and sibling context fill that gap.

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 only parameter 'path' is not described in the schema (coverage 0%) and the tool description does not elaborate on what path means or its expected format. This leaves the parameter semantics ambiguous.

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 tool's purpose ('Read a UTF-8 text file') and distinguishes it from sibling tools like write_text_file or download_file_base64 by specifying the file type.

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 mentions a size limit constraint but does not explicitly explain when to use this tool over alternatives (e.g., download_file_base64 for binary files). Usage context is implied but not stated.

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