read_file

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

The readOnlyHint annotation is complemented by concrete behavioral detail: the 100000-character truncation threshold, the truncated flag in the response, and the interaction with write_file when a file was only partially read. This goes well beyond the annotation.

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, with only three purposeful sentences. Every sentence adds useful information: what the tool does, its truncation behavior, and a critical safety interaction with write_file.

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 definition is complete for a read operation: it identifies the resource, covers truncation and full-file reading, explains consequences of partial reads, and an output schema exists so return values need not be described in prose.

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 100%, so the baseline is 3. The main description repeats the full parameter's truncation behavior rather than adding substantial new param semantics beyond the schema, though it does usefully tie full=True to the write_file safeguard.

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 opens with a specific verb and resource: 'Read a text file from an Overleaf project.' It clearly distinguishes this tool from siblings like list_files and write_file, and the truncation/write_file behavior reinforces its role as a read operation.

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 explicitly explains when full=True is necessary and warns that write_file will refuse to replace a partially-read file. The schema adds 'prefer edit_file for a targeted change,' giving clear guidance on choosing between read_file and edit_file.

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