ezbiz-govcon has 4 tools with Zod schemas and descriptions visible in server.ts. Tool naming follows action-verb conventions (search, analyze, tracker). Descriptions are domain-specific and reasonably detailed (150-250 chars each), well above the 20-char minimum. However, there are significant gaps: (1) No output schemas documented, the code returns `{ content: [{ type: "text", text: result }] }` but does not specify what fields are in `result`; this makes it impossible for LLMs to plan downstream operations or extract structured data. (2) Parameters lack enums for constrained values (e.g., set_aside accepts '8a', 'HUBZone', 'SDVOSB', 'WOSB', 'SBA', 'all' but these are described as free-form strings, not enums); LLMs will hallucinate invalid values. (3) No error handling guidance, the code passes errors as plain text with no recovery hints. (4) Missing parameter descriptions for optional filters (naics, agency, fiscal_year are described but lack format/constraint details). (5) No pagination support documented, tools that return lists (competitor wins, agency spending) have no limit, offset, or cursor parameters, risking context window exhaustion. Naming is clear and verb-first; descriptions are above-average; but schemas, error handling, and composition patterns are weak.

• Add JSON Schema output schema to each tool. Document the structure of returned objects, e.g. { opportunities: [{ id, title, agency, due_date, naics, values_range }], total, next_cursor }. This enables LLMs to extract specific fields and chain to follow-up queries.
• Convert constrained parameters to Zod enums. Change z.string() to z.enum(['8a', 'HUBZone', 'SDVOSB', 'WOSB', 'SBA', 'all']) for set_aside_type and set_aside. This prevents hallucinated values and self-documents valid options.
• Add pagination parameters. Add limit (1 - 100, default 20), offset or cursor, and total_count to response. Cap result sets at 20-50 items per call to control context window growth.
• Implement error recovery hints. On API failures, return structured errors: { error_code, error_message, recovery_hint, retry_after_seconds }. Example: { error_code: 'SERVICE_TIMEOUT', message: 'SAM.gov API timeout', recovery_hint: 'Try again in 30s or use a broader search term', retry_after: 30 }.
• Add format constraints to optional parameters. Update descriptions: 'naics (string, 6-digit NAICS code, e.g. 541512)', 'fiscal_year (string, 4-digit year, e.g. 2025)', 'company (string, exact or partial company name, case-insensitive)'.
• Add tool annotations. Use server.tool(..., { ...schema }, { readOnlyHint: true }) to explicitly mark all tools as read-only. This signals safety and prevents LLM hesitation.
• Document what data each tool draws from. Clarify: search_contracts → SAM.gov realtime, analyze_agency → USASpending.gov historical, competitor_win_analysis → FPDS awarded contracts, set_aside_tracker → aggregated SBA/agency set-aside data. This helps LLMs choose the right tool for the task.

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

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry