Read Text File

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

Annotations provide readOnlyHint=true, and the description adds valuable context: handles text encodings, provides detailed error messages, operates on text regardless of extension, and directory restrictions. No contradiction with annotations.

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?

Front-loaded with core purpose, followed by usage guidance and behavioral details in clear, efficient sentences. Every sentence adds value without redundancy.

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 annotations cover safety, output schema exists (so return values needn't be explained), and the description provides clear purpose, usage, and behavioral context, it is complete for this read-only tool with moderate complexity.

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 67% (path lacks description, head/tail have descriptions). The description adds meaning by explaining the purpose of head/tail parameters ('read only the first N lines'/'read only the last N lines') and clarifies that path is for file access, compensating for the partial schema coverage.

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 specific action ('Read the complete contents of a file'), the resource ('file from the file system'), and distinguishes it from siblings by specifying it operates 'as text' (vs. read_media_file) and for 'single file' (vs. read_multiple_files).

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?

Explicitly states when to use ('when you need to examine the contents of a single file'), provides alternatives via parameters (head/tail for partial reading), and sets boundaries ('Only works within allowed directories').

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