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

With no annotations provided, the description carries the behavioral disclosure burden. It clearly states that the tool returns content directly and is scoped to text files, implicitly ruling out binary files. It does not mention size limits or encoding edge cases, but for a simple read operation the key behavior is disclosed.

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?

Two tight sentences front-load the core behavior and return format, then address the binary-file exception. No wasted words or redundant restatement of the schema.

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 read tool with no output schema, the description covers purpose, return behavior, and boundary cases. It is slightly incomplete regarding failure behavior for binary or missing files, but this is minor given the explicit alternative route.

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 (fileId) is documented in the schema with 100% coverage, including its provenance from list_files or entry details. The description adds no additional parameter-level meaning, so the schema baseline of 3 applies.

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?

States a specific action ('Read text file content') and resource, with concrete formats (code, Markdown, JSON, CSV) and explicit return behavior ('Returns content directly'). This clearly distinguishes it from file-management siblings like list_files, upload_file, and delete_file.

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?

Provides explicit when-to-use (text files) and when-not-to-use (binary files), naming an alternative approach (list_files + download). However, 'download' is not listed among the sibling tools, so the alternative is less actionable than if it named an actual available tool.

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