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

Annotations already declare this a safe, idempotent, non-destructive read, so the bar is lower; the description still adds real context the annotations do not cover—the 2 MiB size cap, the base64-versus-UTF-8 encoding behavior, and the fact that admin-configurable MCP approvals plus business workflow approvals gate access. It does not say what happens when a document exceeds 2 MiB or is not authorized, but overall it meaningfully enriches the behavioral picture.

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 core operational facts (encoding, size cap, approvals) are present and reasonably front-loaded, but the first sentence is generic filler that consumes roughly a third of the text without adding selection value. Trimming it would leave a tighter, more useful definition.

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?

An output schema exists, so return values need no explanation, and the annotations cover the safety profile. However, for a single-parameter tool whose schema is entirely undocumented, the absence of any guidance on documentId sourcing leaves a practical gap an agent would hit on first invocation. Approval and size behavior are adequately covered.

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 0% description coverage on its single documentId parameter, so the description carries the full burden and fails to mention it. It never explains that documentId is a UUID identifying a task document, nor how an agent should obtain one; only the word 'task' indirectly hints at the expected scope.

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 second sentence states a specific verb and resource—reading task file bytes as base64 or UTF-8 text—which is enough to tell it apart from listing or attaching tools. The opening sentence ('working with RetailHardHat documents records') is boilerplate and never explicitly contrasts this with the sibling read_project_document, read_site_document, or read_rfp_document, so sibling differentiation is only implicit in the name.

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?

'Use this when working with RetailHardHat documents records in the connected organization' is a broad context cue but not an explicit when/when-not rule. There is no pointer to list_task_documents for obtaining a document ID, nor any statement about when to prefer this over other read_*_document siblings. Use is only implied by the resource name.

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