Server has 9 tools with complete input schemas and descriptions. Naming follows verb_noun convention (read_file, list_files, write_file, run_command, web_search, fetch_url, submit_job, get_job, finish). Descriptions are present and substantive (avg ~120 chars), exceeding the 10-char minimum. However, parameter descriptions are sparse or missing in several tools (web_search lacks query format guidance; submit_job's job_spec is underdocumented; fetch_url lacks SSRF detail in schema). Output schemas are not formally documented in the tool definitions. Error handling is present in code (ToolError class, timeout handling, SSRF guards) but not surfaced in tool descriptions. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk profiles (write_file, run_command, submit_job are destructive). Parameter constraints (e.g., timeout_sec range, query format) are implemented in code but not declared in schemas.

• Add tool annotations to all tools: set readOnlyHint=true for read_file, list_files, web_search, fetch_url, get_job, finish; set destructiveHint=true for write_file, run_command, submit_job. This enables agents to reason about side effects.
• Document output schemas for each tool. E.g., read_file returns {type: 'string', description: 'File contents as UTF-8 text'}; list_files returns {type: 'string', description: 'Newline-separated file paths relative to workspace, or "(empty)" if no files'}. Include this in the tool definition or a separate outputSchema field.
• Expand submit_job's job_spec parameter schema. Replace the bare 'object' with a detailed schema showing required/optional fields, types, and constraints. E.g., {type: 'object', properties: {name: {type: 'string'}, ...}, required: ['name']}. Reference the contract manifest or Rockie API docs.
• Add parameter constraints to schemas: timeout_sec should have minimum: 1, maximum: 3600 (or appropriate limit). query should have minLength: 1, maxLength: 500. These constraints are machine-parseable and prevent invalid LLM inputs.
• Enhance error descriptions in tool docstrings. E.g., fetch_url: 'Fetches a URL and returns readable text. Blocks private/loopback/link-local/metadata ranges (SSRF-guarded). Returns error if URL is unreachable, blocked, or response is non-text.' This guides agents on what to expect and when to retry.