Brook exposes 5 tools with basic schemas visible in BROOK_SCHEMA_CATALOG. All tools have descriptions (10-100 chars, mostly adequate). Input schemas are partially documented in the catalog but lack formal JSON Schema type definitions and constraints. Parameter descriptions exist but are minimal (10-50 chars). No output schemas documented. Error handling is absent from tool definitions. Tools follow a consistent naming pattern (verb_post) but lack clarity on what data is returned or how errors should be handled. This is a typical community-grade server with functional definitions but significant gaps in LLM-optimization and error guidance.

• Document output schemas for all tools. Example: 'checkin_post returns {success: boolean, agent_id: string, session_id: string, active_agents: number}'. This enables LLMs to chain tools and extract IDs for follow-up calls.
• Expand parameter descriptions to 50-100 chars with format/constraint hints. E.g. 'name: Agent identifier (2-64 alphanumeric chars, e.g. agent-001). Must match the name used in checkin_post.'
• Add error handling guidance to tool descriptions. E.g. 'Returns 400 if agent name is invalid (must be 2-64 chars). Returns 409 if agent already checked in, call checkout_post first.'
• Convert BROOK_SCHEMA_CATALOG to formal JSON Schema with type, minLength, maxLength, enum, and pattern constraints. This enables schema validation and LLM constraint awareness.
• Rename tools to follow verb_noun convention without HTTP method suffix: 'push_fleet_telemetry', 'checkin_agent', 'checkout_agent', 'publish_event', 'silence_alert'.