Single tool 'browse_catalog' has critical definition gaps. Input schema is empty object {} with no parameter descriptions. Tool description is minimal (54 chars) and lacks context on what 'catalog' contains, when to use it, or what structure is returned. No output schema documented. The tool appears to be a discovery/listing tool but lacks the guidance patterns (pattern:tool-description) that would help LLMs understand its purpose and expected results. Tool name is acceptable (verb_noun form) but definition quality is severely compromised by missing schemas and sparse descriptions.

• Add comprehensive input schema with typed parameters (e.g., category, limit, offset) and descriptions for each. Use enums for category if applicable.
• Expand tool description to 100 - 200 characters explaining: 'Lists available RTK Motion tools and services. Call this first to discover what capabilities are available before invoking specific tools. Returns tool names, descriptions, and pricing tiers.'
• Document output schema with example structure: array of objects with fields like name, description, category, pricing_model, requires_auth.
• If pagination is supported, add limit and offset/cursor parameters with descriptions and constraints (e.g., 'limit: 1 - 100, default 20').
• Provide explicit tool registration code (not just Python example) showing the full schema, descriptions, and output structure in the server implementation.