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

The annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds one piece of genuine behavioral context: MCP approval requirements are administrator-configurable while business workflow approvals always apply. That is useful but abstract — it does not say whether this specific read call ever blocks on approval, nor does it mention pagination or result caps, which matter for a list tool.

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?

Only one of the three sentences does real work ("Read permit document metadata"); the opening clause is awkward filler ("documents records") and the approval sentence is generic boilerplate repeated across the tool family. It is short, but the useful content is not front-loaded.

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 explained, and annotations cover safety. But with 0% schema coverage on four parameters and no mention of pagination, filtering, or the approval behavior specific to this call, the description leaves an agent under-equipped to invoke it correctly.

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 must carry the burden — and it says nothing about permitId, limit, offset, or search. An agent cannot learn from the text that results are paginated with a default page size of 50, or that 'search' filters metadata within a permit.

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, "Read permit document metadata," gives a specific verb and resource and implicitly distinguishes this list operation from read_permit_document (which fetches content) and from list_permits. However, the surrounding boilerplate ("working with RetailHardHat documents records in the connected organization") is generic and does not name any of the many sibling document-list 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?

The only usage cue is the vague "Use this when working with RetailHardHat documents records," which would apply equally to dozens of document tools in the sibling list. It never states when to choose this over read_permit_document, list_project_documents, list_site_documents, or list_permits, nor does it give prerequisites such as needing an existing permit.

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