The Hermes Action Bridge defines 8 tools with clear semantic structure and descriptions, but has significant gaps in parameter documentation and output schema clarity. Tool descriptions are moderately detailed (90-150 chars), meeting the baseline for discovery, but parameter descriptions are sparse or missing, and output schemas are not documented. The naming convention is consistent (hermes_* prefix with action verbs: capabilities, plan, prepare, execute, draft, approve, reject, request_approval), which is good for discoverability. However, several parameters lack descriptions (e.g., 'contextFiles' array items, 'provider', 'model'), and no tool documents its return schema or pagination behavior. Error handling guidance is minimal, tools declare risk levels (READ_ONLY, WRITE, IRREVERSIBLE, REVERSIBLE) but do not explain recovery steps or actionable error messages. The approval workflow tools (hermes_approve, hermes_reject, hermes_request_approval) form a good composition pattern for managing side effects, but lack clear sequencing documentation. Overall: solid foundation, but underinvested in parameter detail and output documentation.

• Add a 'Returns' section to each tool description documenting the output schema. For example, hermes_capabilities should state: 'Returns an object with {status: string, presets: [{name, description}], policies: [...]}'. This enables LLMs to plan downstream data extraction.
• For every parameter, add a description explaining its purpose, format, and constraints. E.g., 'contextFiles: Array of file paths (relative or absolute) to include as context for the Hermes plan. Each path is validated to exist before execution. Example: ["src/main.ts", "docs/api.md"].'
• Document error scenarios and recovery paths in tool descriptions. E.g., for hermes_execute: 'May fail with: (1) auth_required, user declined confirmation, try again with explicit approval; (2) timeout, increase timeoutSeconds; (3) invalid_preset, verify preset name via hermes_capabilities.'
• Add min/max constraints to numeric parameters using JSON Schema minValue/maxValue and restate in descriptions. E.g., 'maxTurns: integer, 1-100 (default 5). Controls the maximum number of agentic tool-calling iterations before Hermes halts.'
• For hermes_execute, document the 'yolo' parameter security implications: 'Dangerous: when true, skips confirmation dialogs and policy checks. Only enable with explicit user consent. Actions taken with yolo=true are NOT auditable by default.' Consider requiring an extra confirmation parameter if yolo=true.
• Add pagination examples if tools return lists. E.g., hermes_capabilities: 'Returns paginated results with limit=50 default. Supports ?offset=0&limit=20 for retrieval. Total count included in response.'

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

• Relies on Stateful initialize / Mcp-Session-Id (removed; protocol is stateless) - make each request self-contained