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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only the note that MCP approval requirements are org-configurable while business workflow approvals always apply — real context beyond the annotations, but of unclear relevance to a read-only listing call and not explained further. Nothing is said about whether results are paginated or complete.

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 with no bloat, but the informative one ("Read rfp document metadata") is buried in the middle, sandwiched between boilerplate about RetailHardHat and an approvals disclaimer. Front-loading the actual behavior would make it materially more usable.

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 not be described. However, for a paginated list tool with four entirely undocumented parameters, the definition omits the essentials: what entity the documents belong to, whether the result set is capped at 100 and how to page through it, and how it relates to read_rfp_document.

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% across four parameters (rfpId, limit, offset, search), so the description carries the full burden and delivers nothing: it never explains that rfpId selects the parent RFP, that limit/offset paginate (max 100 per page), or that search does a text filter over document names. The only clue is the name 'rfpId'.

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 sentence "Read rfp document metadata" gives a verb (read/list) and resource (RFP document metadata), but it never states the crucial scoping fact — that it returns documents attached to a specific RFP identified by rfpId. It also fails to distinguish itself from the many near-identical siblings (list_project_documents, list_bid_documents, list_permit_documents, read_rfp_document), so an agent must infer the difference from the name 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?

"Use this when working with RetailHardHat documents records in the connected organization" is generic filler that would apply to dozens of sibling tools. There is no when-to-use condition, no exclusion, and no pointer to the alternative tools (read_rfp_document for content vs. list_rfps for the parent records).

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