Harbor exposes 16 tools across multiple domains (crypto, stocks, GitHub, PostgreSQL, internal memory). While all have names and descriptions, critical gaps exist: (1) Most tools lack explicit input schemas in the source code or schemas are inferred rather than directly visible; (2) Parameter descriptions are minimal or missing type constraints; (3) Output schemas are not documented; (4) Three internal tools (harbor_recall, harbor_remember, harbor_http) have empty input objects with no parameters defined, making their behavior opaque; (5) No error handling guidance or recovery patterns visible; (6) No security annotations despite exposing database queries and HTTP tools. The server demonstrates a connector-based architecture (coingecko, yahoo, github, postgresql via TypeScript SDKs), but lacks the rigor expected for production agent tooling. Most external connectors reference source files like 'connectors/coingecko/src/index.ts' without showing the actual schema definitions, making schema assessment impossible beyond the high-level parameter names provided. Conservative scoring reflects inability to verify schemas in source and minimal parameter documentation.

• Provide full TypeScript/Go source for all connector tools. Schema definitions must be visible and reviewable in the source code, not inferred from file paths.
• Define explicit input and output schemas for all 16 tools. Use JSON Schema with proper type declarations (string, object, array) and include all required and optional fields.
• Add parameter constraints: enums for categorical values (e.g., state: ['open', 'closed', 'all']), min/max for numeric limits, regex patterns for format validation. Document these in parameter descriptions, not just schema.
• Document expected response structure for each tool. E.g., 'coingecko.prices returns {[coin_id]: {usd: number, eur: number, ...}} with up to 100 coins per call.'
• Implement error categorization: wrap errors in {code, message, recoveryHint} and indicate retryability. E.g., {code: 'RATE_LIMITED', message: 'CoinGecko API limit exceeded', recoveryHint: 'Wait 60 seconds and retry.'}
• For harbor_recall, harbor_remember, harbor_http: define explicit parameters (keys, values, query, headers, method, etc.) so LLMs understand the interface. Empty input schemas are unusable.
• Add pagination support to list_* tools (github.repos, github.issues, github.pull_requests). Accept limit (1-100, default 20) and page (1-based) or cursor parameters. Return {results: [...], total_count: N, next_page: 2} or cursor.
• Add tool annotations: @readonly for all read-only tools, @destructive for harbor_remember (WRITE), @idempotent where applicable. These guide agent retry logic.