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

The description goes far beyond the hints by revealing internal operational behavior. It explicitly states that the tool verifies 'payment, subscription, access and delivery separately,' giving the agent insight into the nature of the returned data.

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?

The description is highly dense but efficient, ensuring every phrase contributes to either usage context or behavioral disclosure. While slightly verbose, its clarity prevents unnecessary back-and-forth between agent and user.

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?

Given that the annotations cover the safety profile and an output schema exists, the description provides all necessary context for the agent. It defines the scope, verification methods, and when the tool should be considered the source of truth.

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?

Since schema coverage is 100%, the baseline is high. The description adds valuable semantics by clarifying that the provided order_id must be 'Exact order_id returned by checkout or an earlier order response for this connected account,' which reinforces the required data source.

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 clearly states the tool's purpose: to verify the status of an existing account order. It distinguishes itself from general search tools by focusing specifically on post-checkout validation for a connected account.

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 provides extremely precise usage guidelines, instructing the agent to use the tool when facing an uncertain result or immediately after checkout. Crucially, it advises against trusting external sources like payment links, clearly defining the boundaries of the tool's utility.

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