Strong foundation with clear, domain-specific tool names and comprehensive descriptions (avg 180 chars). All 10 tools have explicit schemas with typed parameters and descriptions. Tool annotations (readOnlyHint, destructiveHint) are properly declared. Key gaps: output schemas are not declared (tools emit structuredContent additively but don't validate it), error handling lacks recovery guidance (no 'try search_*' hints), and parameter descriptions could specify format/constraints more explicitly (e.g., jurisdiction codes, filing intent enums). CompanyDocument's dual mode (pdf/text) is well-documented but lacks dry-run confirmation for destructive pdf-save path.

• Declare outputSchema for tools that always return structuredContent (e.g., CompanyResolve, CompanyFinancials). Use Zod shapes matching the structured response format to enable MCP SDK validation and client schema discovery.
• Enhance error messages with recovery hints: 'Company not found. Try CompanyResolve() with a partial name or LEI.' This guides LLM retry logic per pattern:recovery-guide.
• Add enum constraints to 'jurisdiction' and 'intent' parameters in tool schemas. Extract valid values from JURISDICTION_REFERENCE and filing-intent constants, then declare them as Zod enums in inputSchema.
• Add optional limit/offset parameters to CompanyFilings, CompanyInsiders, CompanyOwners, PersonAppointments. Cap default results at 20-50 items and document pagination in descriptions.
• For CompanyDocument mode='pdf', add a dry_run parameter or require explicit confirmation before writing to disk. Return the file path in structuredContent so agents can verify before committing.