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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds an approval-configuration note, but for a read-only single-record fetch that note is ambiguous — it may make an agent hesitate about whether an approval gate applies to a plain read. It adds no information about not-found behavior or that this reads a single record only.

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 short sentences, front-loaded with the usage trigger and the core action. The trailing approval sentence is generic boilerplate that does not earn its place on a deterministic read by primary key, and it dilutes the otherwise crisp statement of purpose.

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-value documentation is not required. However, for a single-parameter lookup the description should say what the ID refers to and how to obtain it, plus what a missing record yields; those gaps remain. The approval caveat is the only behavioral context supplied.

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% for the sole `id` parameter, so the schema gives only a UUID format/pattern without saying what it identifies. The description partially compensates by stating the read is "by ID," implying it is the RFI identifier, but it does not say where that ID comes from (e.g., list_rfis) or what happens with an invalid/unknown 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 description states a specific verb and resource: "Read a rfi by ID," which cleanly separates it from the many write/list siblings like list_rfis and update_rfi. It scopes the resource to RetailHardHat rfis in the connected organization. It does not explicitly name a sibling alternative, but the verb+resource pair is unambiguous.

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 rfis records in the connected organization" restates the tool's domain rather than saying when to pick this over list_rfis (e.g., when you already have an RFI ID) or update_rfi. There are no exclusions, prerequisites, or alternative-routing guidance despite close siblings existing.

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