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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds useful behavioral details beyond annotations: archived pages are excluded by default, results are newest-first, full configuration/product/fields are returned, and forms/events are separate. It does not mention pagination or rate limits, but with annotations carrying the safety profile this is solid.

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-loaded with the core verb and resource, then scoping, defaults, and sibling routing. Four sentences, each carrying distinct operational value, with no redundant 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?

For a list tool with a rich input schema and an output schema, the description covers the key agent needs: what is listed, ordering, default filtering, safety profile, and how to route to sibling tools for IDs or other page types. Return-value details are appropriately left to the output schema.

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 limit, search, status, testmode, ending_before and starting_after in detail. The description adds only one parameter-related semantic: archived pages are left out unless you filter by status. That is helpful but does not materially extend the schema, so baseline 3 is appropriate.

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 ('List the checkout pages'), the scope ('on the Checkout Page account'), ordering ('newest first'), and returned fields ('full configuration, product and fields'). It also distinguishes itself from get_checkout_page/update_checkout_page and from list_forms/list_events, so an agent can select it without opening schemas.

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?

Explicitly says how to find a page id for get_checkout_page and update_checkout_page, clarifies that forms and events are separate page types served by list_forms and list_events, and explains the archived-pages default unless status is filtered. When-to-use and alternatives are both covered.

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