Three meta-tools with solid schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. panelica_find_tools and panelica_describe_tool have good descriptions (100+ chars) and proper input schemas with type definitions. panelica_call accepts arbitrary arguments without documenting expected structure, making it difficult for LLMs to compose calls correctly. No output schemas documented for any tool. Parameter descriptions are present but lack detail on constraints, formats, and valid ranges. The 'arguments' parameter in panelica_call is dangerously underspecified, it accepts 'object' with no schema, forcing LLMs to guess structure.

• Document output schema for each tool. panelica_find_tools should specify: returns array of {name, method, path, category, summary, parameters, body_fields, return_type}. panelica_describe_tool should specify: returns {input_schema, response_type, response_fields}. panelica_call should specify: returns {status, data, error}.
• Add detailed constraints to panelica_find_tools 'query' parameter: 'Space or comma-separated keywords (1-100 chars). Each term must match tool name, path, category, or description. Plurals are stemmed. Minimum 1 keyword required.'
• Replace panelica_call 'arguments' bare object with a documented schema: {type: 'object', properties: {path_params: {type: 'object'}, query_params: {type: 'object'}, body: {type: 'object'}}, description: 'Tool arguments: path parameters (e.g. {id: "123"}), query parameters (e.g. {limit: 10}), and/or body object for POST/PUT/PATCH. See panelica_describe_tool for exact schema per tool.'}
• Add error handling guidance to panelica_call: 'On invalid tool name, returns 404 with available tools. On schema mismatch, returns 400 with required fields. On auth failure, returns 401. On rate limit, returns 429 with retry-after.'
• Rename panelica_call to panelica_execute_tool or panelica_invoke_tool to clarify the action and reduce LLM confusion with generic 'call'.