Read a file

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that the file is on the remote host, but it does not disclose potential behavioral nuances such as encoding, symlink resolution, size limits, or return format. With annotations lowering the bar, a neutral score is appropriate.

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 brief and front-loaded with the verb, but the first sentence 'Read a file.' is redundant with the title and adds no value. The second sentence provides slightly more context. It is not bloated, but the structure wastes one sentence on a tautology.

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 tool with no output schema and 0% parameter coverage, the description is too thin. It does not clarify what the tool returns (raw content, base64, etc.), how errors are surfaced, or how it differs from download_file/stream_download_file. The annotations cover only the safety profile, not operational specifics, so the description leaves important gaps.

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 0%, so the description must compensate for the meaning of path and sessionId, but it does not. It only says 'file from the remote host,' which loosely implies path but provides no explanation of sessionId or any parameter constraints or formats. This is a significant gap.

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 states a clear verb and resource: 'Read a file' and 'Reads the content of a file from the remote host.' It distinguishes from sibling list/write/download tools by focusing on reading content, though it does not explicitly contrast with download_file or stream_download_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?

No usage guidance is provided. The description does not mention when to prefer this tool over alternatives like download_file, list_files_directory, or stream_download_file, nor does it state any exclusions or prerequisites.

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