Five tools with clear verb-noun naming (invoke, register_connector, list_connectors, invoke_connector, delete_connector). Descriptions are present and reasonably detailed (80-150 chars each), explaining WHAT and WHEN. However, input schemas lack critical detail: InvokeSpec and payload parameters are typed as generic 'object' with minimal constraint documentation. No enum constraints, format specifications, or validation rules visible in schemas. Parameter descriptions in code are adequate but schema definitions are underspecified. Error handling is minimal, invoke_connector returns a dict with 'success' and 'error' fields, but no guidance on recovery or retry logic. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels (WRITE, DESTRUCTIVE). Output schemas are not formally documented.

• Define InvokeSpec as a structured Pydantic model with explicit fields (target_url, auth_type, auth_credentials, request_format, response_format) and add JSON Schema descriptions for each. Replace generic 'object' with concrete schema.
• Add tool annotations to all tools: mark list_connectors and invoke_connector with readOnlyHint=true; mark register_connector and delete_connector with destructiveHint=true; mark invoke_connector with idempotentHint=false (since it may have side effects on remote services).
• Enhance error responses with recovery guidance. E.g., 'Connector "foo" not found. Call list_connectors() to see available connectors, or register_connector() to create a new one.'
• Document output schemas explicitly. For invoke, return {success: bool, data: object, error?: string}. For register_connector, return {name: string, description: string, target_url: string (redacted)}. For list_connectors, return [{name, description, target_url (redacted)}].
• Add validation constraints to parameters: name (1-100 chars, alphanumeric + underscore), description (0-500 chars), payload (required, non-empty object). Document in schema descriptions.