claude-bus has well-structured tool definitions with clear, domain-specific descriptions (avg 180 chars) and complete JSON schemas. All 10 tools have explicit names, descriptions, and input schemas with proper type definitions. Naming follows verb_noun convention (bus_list, bus_send, bus_inbox). However, output schemas are not documented, responses are returned as free-text JSON or strings without formal schema declarations. Parameter descriptions are present but some lack constraint details (e.g., 'name' params don't specify format/length). Error handling is minimal, no recovery guidance or categorization. Security considerations are implicit (quarantine/approve pattern) but not explicitly documented in tool descriptions.

• Document output schemas for all tools. E.g., bus_list returns array of {name, state, cwd, pending, me}; bus_send returns {id, from, to, subject, body, timestamp}. Include in tool description or separate schema field.
• Add error recovery guidance. Replace 'This session is not on the bus' with 'This session is not on the bus. Call bus_register({name: "<directory-name>"}) to register it first.'
• Specify parameter constraints in descriptions. E.g., 'name: session name (1-64 alphanumeric + dash, must be unique on bus)' and 'id: message ID from bus_quarantine (UUID format)'.
• Add dry-run or confirmation for destructive ops. E.g., bus_send could accept confirm=true; bus_reject could return {id, from, subject, body} and require explicit approval before deletion.
• Declare tool permissions explicitly. E.g., bus_approve description: 'Requires: approve_messages permission. Releases a quarantined message after user review.'