Single tool 'search_assets' has a basic description (54 chars) and minimal schema. Input schema present with two parameters (q, limit) but lacks type constraints, enums, and detailed parameter descriptions. No output schema documented. The tool definition is inferred from test code rather than explicit registration in source. No error handling guidance, no pagination support despite search results, no field-level documentation. This is a bridge server that proxies to a hosted service, but the local tool definition is incomplete.

• Document the output schema explicitly: return type (array of objects), field names (id, name, url, format, license, etc.), and types. Include example response structure.
• Add parameter constraints: 'limit' should specify min=1, max=100 (or actual API limit). 'q' should specify min length and character restrictions.
• Expand parameter descriptions to 50-100 chars each. E.g., 'q: Search query string (2-200 chars, supports partial model names and tags)' and 'limit: Maximum results to return (1-100, default 20)'.
• Add pagination support: document whether results are paginated, and if so, include cursor/offset and total_count in response schema.
• Document error cases: 'Returns error if query is empty, too short, or API is unreachable. Retry with a simpler query or check network connectivity.'