Stripe MCP has well-structured tool definitions with consistent naming (verb_noun pattern: list_*, get_*) and clear descriptions (avg ~60 chars). All 8 tools have input schemas with type definitions and required field declarations. However, parameter descriptions are sparse or missing for several tools (list_payments lacks limit description; list_invoices lacks limit description). Output schemas are not documented, LLMs cannot predict response structure. Error handling is minimal (generic toError() wrapper). No pagination guidance despite list tools returning arrays. No tool annotations (readOnlyHint, idempotentHint).

• Document output schemas for all tools. Example: get_customer should declare it returns {id, email, name, created, ...}. Use JSDoc or inline schema comments.
• Add missing parameter descriptions: list_payments.limit and list_invoices.limit need 'Max results (1-100)' descriptions matching list_customers.
• Add readOnlyHint: true to all tool definitions in the schema to signal to agents that these tools are safe to call without side effects.
• Enhance list tool descriptions with pagination guidance: 'Returns up to {limit} results, most recent first. Call again with later timestamps to fetch older records.'
• Improve error handling: catch Stripe API errors (e.g., StripeInvalidRequestError) and return actionable messages like 'Customer not found. Verify customer_id starts with cus_' instead of raw error.message.