Single tool 'agy' has a comprehensive input schema with 11 parameters, all properly typed and described. Tool description is clear and actionable (127 chars). Parameters cover a wide range of use cases (query, cwd, add_dir, sandbox, conversation, timeout, env_overrides, stdin_text, etc.) with good granularity. However, output schema is not documented, the tool returns 'structured JSON output from agy's --output-format json envelope' but the actual response structure (fields, types) is not specified. This forces LLMs to guess at response shape and limits downstream tool chaining. Error handling is present in code (directory validation, launch failures, timeouts) but not surfaced in the tool description. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite the tool having WRITE risk. Parameter descriptions are generally good (60-100 chars each) but some lack format/constraint details (e.g., 'timeout' lacks min/max bounds).

• Document the output schema explicitly. Specify the JSON structure returned by agy (e.g., {ok: boolean, status?: string, conversation_id?: string, stdout?: string, stderr?: string, error?: string, returncode?: number}). Include field types and which fields are always present vs. conditional.
• Add tool annotations: set destructiveHint=true (tool executes external commands with side effects) and idempotentHint=false (repeated calls with same input may produce different results if agy state changes).
• Add bounds to 'timeout' parameter: 'Hard timeout in seconds for agy execution (default 660, range 1 - 3600)' to prevent absurd values.
• Clarify 'print_timeout' format in description: 'Timeout value to pass to --print-timeout flag (e.g., "30s" or "30000ms"; consult agy docs for exact format).'
• Enhance tool description with error guidance: 'Returns structured JSON. On success, ok=true and stdout contains agy's response. On failure, ok=false and error explains why (e.g., directory not found, binary not found, timeout). If timeout occurs, consider increasing the timeout parameter and retrying.'

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

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