check_shopify_checkout

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses a real behavioral limit: detection is limited to public pages (legacy checkout scripts and tracking), and admin-only factors are returned as a checklist rather than observed. That tells the agent the results are partial, which is valuable and non-obvious.

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?

A single front-loaded sentence with the deadline context first and the scope qualifier second. Dense but every clause (public pages, legacy scripts/tracking, admin checklist) carries information; only the parenthetical is slightly redundant.

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 one-parameter read-only audit with no output schema, the description covers what is checked, on what surface, and what is deliberately not checked (admin-only items). It stops short of describing the shape of the returned findings, which is the remaining gap.

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?

Only one parameter and schema coverage is 100%, so the schema already explains 'url' with an example. The description restates that it must be a public page URL but adds no format or constraint detail beyond the schema; 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?

Specific verb ('check') plus a precise resource ('Shopify store's exposure to the 2026 checkout extensibility deadlines') and an explicit scope ('from its public pages'). It is clearly distinct from siblings like check_ai_shopping_readiness and check_merchant_center by topic, though it never names them.

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 implied by the framing (audit a store's legacy checkout scripts from public pages), but there is no explicit statement of when to pick this over audit_store or the other check_* siblings, and no stated prerequisites.

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