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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuine context beyond that: results are ordered newest first, the shape of each record (revenue, tip, fees, promotions, metadata, payment provider), and the underlying GET /orders endpoint. It does not describe pagination semantics, though the schema's offset description carries that.

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?

One dense but well-ordered sentence: purpose and parenthetical definition first, then returned fields, then filter options, then the endpoint. The field enumeration is long but each item informs the agent about available data; no filler sentences.

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 no output schema, the description correctly compensates by listing the fields each order returns, and annotations carry the safety profile. Pagination and filtering mechanics live in the schema, so nothing critical is missing, though the list of record fields is illustrative rather than exhaustive.

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 100%, so all six parameters including the source enum and test_mode flag are already fully documented. The description echoes three of the filter dimensions (creation time, purchaser email, source) but adds no format or syntax details beyond the schema, so the baseline 3 applies.

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 states a specific verb+resource ('List orders') and immediately disambiguates the domain term ('the purchases that created gift cards'), which distinguishes it from the singular sibling giftup_get_order. It also enumerates the returned fields and the default sort order, so an agent knows exactly what it gets back.

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?

Usage is only implied: 'Filter by creation time, purchaser email or source' hints at the retrieval scenario, and listing multiple orders implicitly contrasts with giftup_get_order for a single order. There is no explicit when-to-use/when-not statement or named alternative.

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