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

Annotations already declare readOnly/idempotent/non-destructive, so safety needs no restating. The description adds genuinely new context: reads are 'complete' (not truncated) for small files, and large or binary files return a 'temporary' URL, signaling expiry and out-of-band retrieval. It stops short of stating URL lifetime or size limits.

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 sentence that front-loads the primary mode and closes with the fallback. Every clause carries information; no waste.

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 covers the two return shapes (document body vs. temporary URL), which is the key missing structured information. Minor gaps remain around size thresholds and URL expiry, but an agent can call this correctly.

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?

One required parameter (fileId) with 0% schema description coverage, and the description never mentions it or its UUID nature. The 'in Files' phrasing loosely contextualizes the identifier, but the description does not compensate for the empty schema.

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?

A specific verb ('Read') plus resource ('UTF-8 documents in Files') with the dual-mode behavior stated up front. It does not, however, distinguish itself from the sibling get_file or list_files, so an agent cannot rule those out from the description 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?

The description gives an implicit selection rule — small UTF-8 documents get inline content, binary/larger files get a download URL — which is useful. But it never names alternatives (get_file, list_files) or states when a caller should prefer those instead, leaving the boundary to inference.

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