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

Annotations already flag destructiveHint=true, but the description adds information annotations cannot carry: the delete cascades to dependent records, the call is a no-op until a human approves the exact request, and execution requires a separate execute_approved_action call. It also discloses that MCP approval thresholds are admin-configurable while business workflow approvals always apply, which is exactly the operational context an agent needs.

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?

Four sentences, with the substantive delete-scope statement and the approval gating front-loaded after a brief locator clause. The closing sentences about admin-configurable approvals are slightly redundant with the human-approval sentence but earn their place by clarifying who controls the gate.

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 no explanation, and the single required parameter is straightforward. The approval workflow and cascade behavior are covered. The one gap is that "dependent records" is never enumerated and reversibility is not stated, leaving the blast radius partially undefined for a destructive tool.

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 would ideally explain changeRequestId, but the schema itself pins it as a UUID with an explicit pattern, making the type unambiguous. The description adds no meaning about where the ID comes from or how to obtain it. Baseline 3 given the self-describing single parameter.

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?

States the specific verb and resource ("Delete a change request") and adds a scope detail that matters: dependent records are removed too. That distinguishes it from the line-item and document deletion siblings. The opening sentence about "working with RetailHardHat change_requests records" is boilerplate but does anchor the domain.

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?

It names the prerequisite flow (human approval in Settings > MCP, then execute_approved_action), which tells the agent this cannot be completed in one call. However, it never contrasts with alternatives such as update_change_request, delete_change_request_line_item, or delete_change_request_document, so the agent has no explicit routing rule.

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