Coral exposes 5 tools with partial schemas and descriptions. All tools have descriptions (10-200 chars), but input schemas are incomplete or missing type definitions for complex parameters. coral_check_action and coral_request_review accept 'action' as a bare object with no type constraints, violating the schema requirement. Naming is verb-forward (list_, open_, close_, check_, request_) but descriptions lack actionable guidance on when to use each tool vs. alternatives. No output schemas documented. Error handling is mentioned in descriptions but not implemented in visible code. Security-critical tools (open_session, request_review) lack permission gates or scope declarations.

• Define nested schema for 'action' parameter in coral_check_action and coral_request_review. Specify required fields (e.g., 'type' is mandatory), allowed types, and constraints. Example: {"type": "object", "properties": {"type": {"type": "string", "enum": ["navigate", "click", "fill", ...]}}, "required": ["type"]}
• Document output schemas for all tools. coral_open_session must return {session_handle, cdp_url, expires_at}; coral_request_review must return {review_id, status}. Include field types and descriptions.
• Add permission gates and scope declarations. Specify which agent roles can call coral_open_session (e.g., 'requires scope: browser:open'). Log all calls with agent_id, timestamp, action, and decision.
• Expand descriptions to 100-150 chars with explicit guidance: 'Use coral_check_action to pre-flight an action before executing (read-only, counts against rate limit). Use coral_request_review only when check_action returns decision=review_required.'
• Add error handling guidance to descriptions. E.g., 'Returns {decision: "deny", reason: "..."} if policy blocks the action. Retry with a different action or call coral_request_review for operator override.'