Two tools with basic descriptions but critical schema and parameter documentation gaps. shell_echo lacks input validation guidance and error recovery hints. http_get_sandbox has minimal parameter descriptions. Neither tool documents output schemas. Descriptions are present but generic (under 100 chars each). No tool annotations (readOnlyHint/destructiveHint). Parameter types visible in schema but descriptions are sparse. Error handling not documented. No guidance on when to use each tool vs alternatives.

• Add output schema documentation for both tools. E.g., shell_echo should document: {stdout: string, stderr: string, exit_code: int, timed_out: bool}. http_get_sandbox should document: {body: string, status_code: int, headers: object}.
• Expand parameter descriptions with constraints and examples. E.g., 'argv: Array of command arguments (e.g., ["ls", "-la", "/tmp"]). First element must be a binary name in the allowlist. Max 10 args, each ≤256 chars.'
• Remove 'allowlist' from shell_echo parameters. Instead, configure allowed binaries server-side (e.g., via environment variable or config file). The tool should validate argv[0] against this pre-configured list and return a clear error if not allowed.
• Add tool annotations: shell_echo should have destructiveHint=true (can execute arbitrary commands); http_get_sandbox should have readOnlyHint=true (no side effects).
• Document error scenarios and recovery guidance. E.g., 'If command times out (15s), the tool returns exit_code=-1 and timed_out=true. Retry with a simpler command or increase timeout if appropriate. If binary not in allowlist, returns error with list of allowed binaries.'

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

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