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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered by structured data. The description adds the fact that approvals are governed by org-configurable MCP settings plus business workflow approvals, which is contextual but boilerplate and oddly framed for a pure read tool. It adds nothing about pagination behavior, default page size, or ordering.

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 two sentences and front-loaded with the use case, which is good. But the second sentence is administrative boilerplate about MCP approval configuration that does not help an agent invoke a read-only list operation, so space is spent on low-value content while filtering/pagination stays unaddressed.

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. But for a list tool with four undocumented filter/paging parameters and no indication of default ordering or scope, the description leaves out the information an agent most needs to call 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 (limit, offset, search, siteId) and the description says nothing about any of them. The names are largely self-explanatory, which prevents a 1, but there is no explanation of what `search` matches, whether siteId scopes results, or what the default/max page size implies.

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 it reads change_requests records in the connected organization, which is a recognizable verb+resource. However it never states the listing scope (all records vs. filtered), never mentions pagination, and does not distinguish this from siblings like get_change_request, list_change_request_line_items, or list_change_request_approvals. An agent can guess its role only from the name.

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 change_requests records" is close to a restatement rather than a condition for selecting this tool. There is no statement of when to prefer this over get_change_request for a single record, or over the line-item/approval list siblings.

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