Single tool with basic schema and description. Tool name 'query_logs' is appropriately verb-noun formatted. Description exists but lacks critical context: no mention of prerequisites (API token setup), when to use vs alternatives, or what the return structure contains. Parameter descriptions are present but generic, 'The log query string' doesn't explain syntax, constraints, or examples. Schema includes types but lacks enums, patterns, or min/max constraints. No output schema documented. Error handling is minimal: TimeoutError and ValueError are raised but provide no recovery guidance. The tool accepts both explicit timestamps and simple_time_range with precedence rules, but this dependency is buried in the docstring rather than clearly documented in parameter descriptions. No pagination guidance despite the page_token parameter suggesting multi-page results.

• Document the complete output schema: 'Returns: {query_id: str, is_finished: bool, logs: [{timestamp: str, message: str, ...}], next_page_token: str | null}'. Include all fields the LLM might need.
• Replace example timestamps in descriptions with format constraints: 'ISO 8601 format: YYYY-MM-DDTHH:MM:SS.000Z' instead of 'e.g. 2025-05-08T18:08:35.000Z'.
• Clarify parameter relationships: Mark simple_time_range as 'optional; if provided, overrides start_time and end_time'. Mark start_time and end_time as 'required if simple_time_range not provided'.
• Add pagination guidance to tool description: 'Results are paginated. Use page_token from the response to fetch the next page. Limit results to 100 logs per call.'
• Enhance error messages with recovery steps: Catch TimeoutError and return 'Query timed out after 10 attempts. Try a shorter time range or simpler query. Retry with simple_time_range="1h".' instead of a bare exception.

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

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