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

Annotations already declare readOnlyHint=true, destructiveHint=false and closed-world, so the safety profile is covered. The description usefully adds what a single-purchase read expands into (lines, refunds, holds), but says nothing about pagination via cursor, the 50-item cap, or workspace scoping.

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 front-loaded sentence with no filler; the list-first ordering matches the default invocation pattern.

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?

A four-parameter tool with zero parameter documentation, no output schema, and no explanation of the required workspace or the cursor/limit pair leaves real gaps for correct invocation. The description adequately covers what the tool is but not how to call it correctly.

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% across four parameters. The description implies the role of 'purchase' (selects the single record), but 'workspace' (required), 'limit' (1-50) and 'cursor' are entirely undocumented in both schema and prose, so an agent must guess at required scoping and paging semantics.

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?

Names a specific resource (Stripe Checkout purchases) and two distinct operations (list recent vs. read one with lines/refunds/holds), which lets an agent tell it apart from stripe_checkout_purchases_update. It stops short of naming the write sibling explicitly, so differentiation is implied rather than stated.

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 description conveys the mode split – omit 'purchase' to list recent, supply it to read a single purchase with its sub-objects – which is usable guidance. It gives no guidance against other read tools (orders_get, payments_get, checkout_get, commerce_get) that might also return purchase data, so an agent has no basis for choosing among them.

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