Two tools with minimal descriptions (both under 50 chars) and incomplete parameter documentation. fetch_current_user_data has a single parameter 'context' with a generic description; fetch_aap_controller_jobs_list has three parameters (order_by, page, page_size) with minimal guidance on valid values, ranges, or constraints. No output schemas documented. No error handling guidance. Parameter descriptions lack actionable constraints (e.g., no enum for order_by, no min/max for page/page_size). Both tools return raw response.text, which is unstructured and requires LLM parsing. No indication of what fields the LLM should expect.

• Add structured output schemas. Document what fields the response JSON contains (e.g., 'Returns {id, username, email, created_at}' for user data). Parse response.text into a dict and return only relevant fields.
• Expand tool descriptions to 100 - 200 chars. Include WHEN to use each tool: 'Fetch the authenticated user's profile (name, email, roles). Call this first to verify credentials and get the user ID for subsequent API calls.'
• Add parameter constraints. For order_by, document valid fields: 'Field to order results by (e.g., -finished, -created, name). Prefix with - for descending order.' For page_size, add bounds: 'Number of results per page (1 - 100, default 10).'
• Implement error handling with recovery hints. Catch httpx.HTTPError and return: 'API request failed: {status_code}. If 401, check your authentication token. If 500, retry after 30 seconds.'
• Add pagination guidance. Document that fetch_aap_controller_jobs_list returns paginated results; explain how to use page and page_size to iterate, and what the response structure includes (e.g., 'count', 'next', 'results').

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry