Single tool 'audit_store' has a basic description (89 chars) but critically lacks input parameter descriptions. The schema defines a 'url' parameter with only a type string and minimal description ('The store URL to audit (e.g., https://your-store.com)'). No output schema is documented anywhere in the codebase. The tool name is reasonable (verb_noun form) but the overall definition is sparse. No error handling guidance, no pagination, no structured output specification. The client examples show HTTP transport but the server implementation is not visible in the provided source, making it impossible to verify actual tool registration, error handling, or response structure.

• Document the complete output schema. Specify what fields the audit returns (e.g., performance_score, seo_issues, configuration_warnings, recommendations). Include data types and whether fields are always present or conditional.
• Expand parameter description to: 'The Shopify store URL to audit (must be a valid HTTPS URL pointing to a live Shopify store, e.g., https://example-store.myshopify.com). The server will crawl the homepage and analyze performance, SEO, and store configuration.'
• Add error handling guidance: 'If the URL is unreachable or not a Shopify store, the tool returns an error with the reason. Timeouts (>30s) indicate the store is slow or offline, suggest retrying or checking store status.'
• Add tool annotations to the schema: include 'readOnlyHint: true' to signal the tool does not modify state, and 'idempotentHint: true' if repeated calls with the same URL produce the same results.
• Provide example output in documentation (separate from the schema) showing the structure of a successful audit result, including field names, types, and sample values.