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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description only needs to add non-obvious context — and it does: the official-status-page provenance and the '1 credit' cost, which matters for an agent budgeting calls. It does not describe the shape of the status payload, which is the main remaining gap.

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 what is checked, then why it matters, then provenance and cost. Four sentences is slightly more than strictly needed — the 'Critical for merchants...' sentence overlaps with the first — but nothing 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?

For a zero-parameter read tool with no output schema, the description tells the agent what domains are covered (storefront, admin, checkout, payments, API, apps) so the return values are predictable. Only the status vocabulary (e.g., operational/degraded/outage per component) is left implicit.

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?

The tool takes zero parameters, so the schema imposes nothing to explain and the baseline is 4. The description correctly describes a no-argument global check rather than implying any filtering options.

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 + resource: 'Check the status of Shopify storefronts, admin, and checkout', with the monitored surfaces (payment processing, API endpoints, third-party apps) enumerated. The vendor-specific name plus the explicit component list makes it unmistakable against the many other *_status siblings.

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?

'Critical for merchants investigating store downtime or checkout disruptions' gives a concrete triggering scenario, and 'directly from Shopify's official status page' clarifies the source of truth. It stops short of stating exclusions (e.g., that it does not diagnose your own store's configuration or orders), so it is clear context rather than full when/when-not guidance.

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