INSEE MCP has one tool with a strong, detailed description (194 chars) that clearly states WHEN to use it (French company lookups) and WHAT it returns. The input schema is present with proper types and descriptions. However, the tool name 'insee_company' lacks a verb prefix (should be 'get_company' or 'lookup_company'), and the output schema is not documented, callers cannot predict the response structure. The _apiKey parameter violates secret-injection patterns by exposing it as a tool parameter, though the code comment acknowledges this is intentional for flexibility. Error handling returns structured error objects but lacks recovery guidance (e.g., 'Try with a different identifier format').

• Rename 'insee_company' to 'get_company' or 'lookup_company' to signal the retrieval action and improve LLM tool selection.
• Document the output schema in the tool description or as a separate schema field. Example: 'Returns {identifier, type, source, summary: {siren, name, naf_ape, ...}, data}'.
• Remove _apiKey from tool parameters. Move API key injection to server-side environment variables (PLATFORM_INSEE_KEY) only. If per-user keys are needed, use a separate configuration mechanism, not tool params.
• Enhance error messages with actionable recovery steps. E.g., 'Invalid identifier: must be 9-digit SIREN or 14-digit SIRET. Got: "123". Try: "552032534" (Danone).'
• Add a 'fields' parameter to allow callers to request only summary or full data, reducing response size and token cost for common queries.