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

Annotations already cover safety (readOnlyHint, destructiveHint=false, openWorldHint), so the bar is lower. The description still adds real value beyond them: ordering ('newest first'), timezone ('every date is in UTC'), pagination mechanics ('pass the cursor to read the next page'), and an auth prerequisite (Cotlet API key with app access).

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?

Front-loads the resource and its returned fields, then adds ordering, timezone, pagination, and auth in sequence. Slightly wordy with mild redundancy (the Customers page referenced twice), but every sentence carries information and none is filler.

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?

No output schema exists, yet the description names the returned fields well enough for an agent to know what comes back, and it covers pagination, ordering, timezone, and authentication for a nine-parameter read tool. Only a fuller return-value or error description is missing.

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 the schema already documents all nine parameters including the two enums. The description restates the filter list (email, product, order date, order ID, status, shipping) but adds little syntax or format detail beyond what the schema provides, warranting the baseline 3.

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 a specific verb and resource ('Orders from the Customers page') and enumerates the returned fields (buyer email, items, amounts, status, date), so an agent understands exactly what a call yields. It does not explicitly distinguish itself from siblings like payhip_get_order or payhip_get_sales_report, but the list-shaped purpose is unambiguous.

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?

Describes the available filter set (email, product, order date, order ID, status, shipping) which implies the retrieval use case, and explains pagination via cursor. However it never states when to prefer this over payhip_get_order for a single lookup or payhip_get_sales_report for aggregates, so no exclusions or alternatives are offered.

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