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 covered. The description adds one genuinely useful behavioural note — that MCP approval requirements are org-configurable and business workflow approvals always apply — which warns the agent a call may be gated. It says nothing about ordering, pagination, or result shape.

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 the second sentence earns its place; the first is boilerplate that restates the tool domain, and the third is generic approval policy text. The actual purpose is buried mid-paragraph rather than 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?

With a rich annotation set, an output schema, and a conventional four-parameter surface, most of the calling contract is covered elsewhere. The remaining gap is scoping ambiguity against the many other list_*_documents siblings, which the description does not resolve.

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%, so the description must carry parameter meaning, and it carries none. It never mentions that taskId is required, nor what 'search' filters on or how limit/offset paginate.

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 task document metadata" gives a specific verb and resource, and the word "metadata" usefully separates it from read_task_document, which presumably returns content. However, the opening sentence ("Use this when working with RetailHardHat documents records in the connected organization") is generic filler, and the description never says it returns a list or how it differs from list_project_documents / list_site_documents.

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 framing is the tautological "Use this when working with RetailHardHat documents records," which gives no condition, prerequisite, or alternative. An agent cannot tell from this text whether to call it or read_task_document / list_project_documents for a given need.

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