This is a PFC (Proof of Concept) reference implementation for delegation chain governance, not a production MCP server. The three tools (firecrawl_scrape, manage_crm_objects, create_draft) are stub connectors defined in src/connectors.ts and examples/external-consumer/consume.ts. Tool definitions are inferred from code comments and type hints rather than explicit MCP tool registration. Input schemas are partially visible but lack complete parameter descriptions. Descriptions are present but generic (10-50 chars). No output schemas documented. No error handling guidance. The codebase focuses on cryptographic chain verification and issuance, not on tool quality or LLM-optimized definitions.

• Implement explicit MCP tool registration via server.setRequestHandler('tools/list', ...) with full JSON Schema definitions for each tool. Include name, description (150-250 chars), input schema with typed parameters, and documented output schema.
• Expand tool descriptions to 150-250 characters. Example: 'firecrawl_scrape: Fetch and parse web page content using Firecrawl. Returns structured data in specified format (markdown, html, json). Use when you need to extract information from a URL. Requires valid URL; fails on 404, timeout, or rate limit.'
• Document output schemas for each tool. Example: firecrawl_scrape returns {content: string, format: string, url: string, status: number}. manage_crm_objects returns {id: string, created: boolean, updated: boolean, errors?: string[]}.
• Add parameter descriptions and constraints. Example: 'formats' → 'Output format(s) as array. Valid values: markdown, html, json. Default: [markdown].' 'properties' → 'Object properties as key-value pairs. Required fields depend on objectType (e.g., contacts require email).'
• Add error handling guidance to descriptions. Example: 'If URL is invalid or unreachable, returns error with suggestion to verify URL. If rate limited, retry after 60 seconds.' Include recovery patterns for each failure mode.