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

Annotations already declare readOnlyHint=true, idempotent=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds an authorization note that MCP approval requirements are org-configurable and business workflow approvals always apply, which is real context beyond the annotations, but it reads as boilerplate shared across the toolset rather than something specific to this read operation, and pagination/sorting behavior (limit/offset) goes unmentioned.

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, but the operative content ("Read site document folders") is buried in the middle while the first sentence is throwaway boilerplate. The approval sentence is stock policy text rather than information needed to invoke this specific tool.

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 needn't be described, and annotations cover safety. Still, for a paginated list tool with four undocumented parameters and a search filter, the description gives no guidance on required siteId, paging defaults, or how search narrows folders, which is the core information an agent needs.

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, so the description carries the full burden and fails to meet it. Only the implicit site scoping ("site document folders") hints at siteId; limit, offset, and especially search (server-side filtering by name?) are never explained, leaving the agent to guess how to narrow results or page.

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?

"Read site document folders" gives a resource and a read verb, so the basic operation is identifiable. But it never distinguishes this list operation from siblings like get_document_folder, list_site_documents, or create/update_document_folder, and the leading sentence ("working with RetailHardHat documents records") is generic filler that could describe any of dozens of sibling tools.

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 near-universal trigger that applies to nearly every document sibling, so it does not route the agent. There is no statement of when-not-to-use, no mention of get_document_folder for a single folder, and no prerequisite (e.g., needing a siteId) called out.

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