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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is fully covered. The description adds something the annotations cannot: that MCP approval requirements are org-admin configurable while business workflow approvals always apply. That is useful but generic boilerplate that reads identically across tools rather than tool-specific behavior.

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 little waste, but the ordering is poor: the vague 'when working with...' framing leads, while the actual purpose ('Read carrier tracking history') is buried in the middle. The approval sentence is generic and could be trimmed without loss.

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 the read-only profile. However, for a two-required-UUID tool with zero schema descriptions, the definition should clarify what the IDs identify and how this differs from refresh_purchase_tracking; those gaps leave it only adequate.

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% and the description never names or explains siteId or purchaseItemId. It implies scenarios involving a purchase item ('purchase_lists records', 'carrier tracking history') but does not state that both UUIDs are required or what 'site' scoping means, so an agent gets no help beyond raw JSON Schema patterns.

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 gives a real verb and resource: 'Read carrier tracking history,' which tells an agent this is a read of tracking events for a purchase item. The opening frame ('working with RetailHardHat purchase_lists records') is vague and slightly misaligned with the tool's actual resource (tracking events), and nothing distinguishes it from the very similar sibling refresh_purchase_tracking.

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 trigger is 'when working with RetailHardHat purchase_lists records in the connected organization,' which is a context restatement rather than a condition for choosing this tool. There is no when-not guidance and no mention of refresh_purchase_tracking, the obvious sibling an agent would need to disambiguate against.

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