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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description goes beyond them by disclosing the conditional return behavior (inline content vs temporary download URL), which is the key non-obvious trait for this tool. It omits the size threshold that triggers the switch and the URL's expiry window.

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?

A single front-loaded sentence with no filler; the primary mode (inline read) precedes the fallback (download URL), which is the correct emphasis.

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?

With no output schema, the description correctly explains what comes back (document content or a download URL) and why the branch occurs, covering the main return-value ambiguity. It is slightly thin on error/edge behavior for a nonexistent file, but adequate for a single-param read tool whose safety annotations are complete.

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 schema has 1 parameter with 0% description coverage, and the description never mentions fileId, its UUID format, or where it can be sourced. Since the schema does not compensate, the description should have carried the burden and does not.

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 names a specific verb (Read) and resource (Files) and, unusually, splits the behavior into two concrete outcomes: inline UTF-8 content for small documents versus a temporary download URL for binary/larger files. That is clear purpose. It stops short of distinguishing itself from the sibling get_file, so an agent still cannot tell the two apart from the text alone.

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?

Usage is only implicit: small UTF-8 documents yield content, binary/larger files yield a URL. It never states when to choose this over the near-identical get_file sibling, nor any prerequisite such as needing a fileId from list_files or find_assets.

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