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

Annotations already declare readOnly=true and destructive=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: which formats yield text, that images return as the picture itself, and that video/audio fail. No auth or rate-limit context, but the output-shape disclosure is valuable.

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 dense sentences, front-loaded with the core action and scope, then the format/limitation detail. No filler; every clause (formats, image handling, exclusions) carries information an agent needs.

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?

No output schema exists, and the description covers what comes back (text vs. picture), format support, and the alternative for images. It leaves max_chars behavior to the schema and doesn't discuss size limits or truncation beyond that, a minor gap for a file-read tool.

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 coverage is 50% and the undocumented parameter is 'url'. The description supplies exactly that missing meaning — a URL from list_record_files, a record, or an email attachment — while max_chars is already documented in the schema. Good compensation for the coverage 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?

States a specific verb (Read) and resource (text of a file in this workspace) and explicitly enumerates supported formats. It also distinguishes itself from view_images and implicitly from list_record_files by naming the URL source.

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?

Tells the agent where the URL comes from (list_record_files, a record, or an email attachment), routes image-heavy cases to view_images ('does up to 10 at once'), and excludes video/audio. It does not address the read_email_thread sibling, but the when/when-not coverage is otherwise strong.

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