XOne/Unsloth Studio exposes 4 tools with minimal documentation. Tool names lack action verbs (search_knowledge_base, search_conversation are acceptable; render_html and execute_tool are vague). Descriptions are present but extremely brief (10-50 chars), below the 194-char baseline for production tools. Input schemas are visible but sparse: only 1-2 parameters per tool with minimal type information. No output schemas documented. No error handling guidance. No parameter constraints (enums, ranges, formats). The execute_tool parameter 'parameters' is an untyped object, inviting hallucinated payloads. No evidence of idempotency, pagination, or composition patterns.

• Expand tool descriptions to 100-250 characters. Include WHAT (e.g., 'Searches the knowledge base for passages matching a query'), WHEN (e.g., 'Use when the user asks a question about stored documents'), and WHAT IT RETURNS (e.g., 'Returns up to 10 passages with relevance scores').
• Rename render_html to display_html_content and execute_tool to invoke_external_tool. Add descriptions clarifying the difference between them and when each is appropriate.
• Document output schemas for all tools. E.g., search_knowledge_base should return {passages: [{id, text, score, source}], total_count, next_cursor}. This enables chaining and pagination.
• Add parameter constraints: search_knowledge_base.query should have minLength: 1, maxLength: 500. execute_tool.parameters should be a typed object with known keys, not a free-form object.
• Add error handling guidance in descriptions: 'If no results found, try a broader query or check knowledge_base_status. If the tool times out, retry with a shorter query.'