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

Goes well beyond the annotations by disclosing concrete behavior: output encoding (base64 bytes vs UTF-8 text for text files), a hard 2 MiB size ceiling, an authorization gate ('authorized'), and that organization-configurable MCP approvals plus business workflow approvals may apply. Annotations already cover read-only/idempotent safety, so this added operational context is the right kind of contribution; only the missing detail is what happens when the 2 MiB limit is exceeded.

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?

Three sentences, and the third — approvals may be configurable but business workflow approvals always apply — is genuinely load-bearing. However, the leading sentence is filler that restates the product domain rather than front-loading the actual capability, so the useful content arrives second.

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?

Output schema exists, so return-shape explanation is rightly omitted, and encoding plus the 2 MiB cap are covered. What's missing for a single-parameter binary-read tool is how the caller gets a valid documentId and how to handle an oversized file, leaving a real gap in callability.

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% — documentId has only a uuid format and pattern, no explanation of what it identifies or where an agent obtains one. The description never mentions the documentId parameter at all, so it does not compensate for that gap; the note about 'rfp file' hints at the target resource but gives no guidance on sourcing or validating the ID.

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 gives a specific verb and resource: 'Read authorized rfp file bytes as base64, or UTF-8 text for text files,' which clearly separates this from write-side siblings like update_rfp_document or delete_rfp_document. The opening sentence ('working with RetailHardHat documents records') is vague boilerplate, and it never names read_bid_document / read_permit_document / list_rfp_documents as the alternatives, so differentiation is only partial.

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 generic trigger that would apply to dozens of sibling read_*_document tools. There is no guidance on when to reach for this versus list_rfp_documents (to obtain an ID) or get_rfp (for metadata), and no stated prerequisites such as 'the documentId must come from list_rfp_documents.'

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