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

The annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description does add genuine context beyond the annotations: that MCP approval requirements are administrator-configurable and business workflow approvals always apply, which an agent should know before calling. It still omits pagination/return behavior, so it is valuable but not rich.

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 wasted wording, but the lead sentence is generic vendor boilerplate rather than the actual operation, so the useful information ('Read project document metadata') is not front-loaded. It is brief but not optimally structured.

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. However, for a paginated four-parameter list tool with 0% schema coverage, the description leaves the parameters and the sibling distinction (single-document read vs. other document scopes) entirely undocumented.

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 four parameters (projectId, limit, offset, search), and the description mentions none of them or their semantics. No explanation of default page size, pagination, or what 'search' filters on, so the agent gets zero help beyond raw schema types.

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 says 'Read project document metadata', which conveys the verb and resource, but it is phrased as 'working with RetailHardHat documents records' which is vague branding rather than a precise operation. It never distinguishes listing from siblings like read_project_document or list_site_documents, so the agent must infer the difference from the tool 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 boilerplate context, not a when-to-use rule. There is no guidance on choosing this over read_project_document for a single file or list_site_documents/list_closeout_documents for other document scopes.

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