Convertica MCP has two well-named, action-oriented tools with clear descriptions and structured schemas. However, several quality gaps prevent a higher score: (1) The `convert_file` tool's input schema uses `additionalProperties` with oneOf for `options`, which is less precise than explicit parameter definitions, this forces LLMs to guess at valid option names without enumeration or per-option descriptions. (2) Parameter descriptions in the schema are present but terse (many under 50 chars); they lack actionable guidance on constraints, formats, or dependencies. (3) No output schema is documented, LLMs cannot know what fields `convert_file` returns beyond what the code reveals (saved, bytes, tool). (4) The `list_converters` tool accepts an empty input schema but returns JSON text rather than structured object fields, making the output harder to parse programmatically. (5) Error handling is functional (apiKey() check, file validation, HTTP status hints) but lacks guidance on retry behavior or when errors are retryable.

• Document output schemas formally. For `convert_file`, add a `returns` section to the description or tool registration specifying: `{saved: string (absolute path), bytes: number (file size in bytes), tool: string (slug used)}`.
• Replace the `additionalProperties` `options` parameter with explicit per-tool option definitions, or restructure `convert_file` to accept a required `catalog_entry` (from `list_converters`) plus a static set of common options (quality, pages, etc.) with enums and descriptions.
• Expand parameter descriptions to 80 - 150 chars each, including format hints, constraints, and dependency notes. E.g., `files: 'Array of absolute file paths (must exist). Order matters for multi-file tools. Required unless tool.noFile is true.'`
• Restructure `list_converters` output as `{type: 'text', text: JSON.stringify({converters: [{slug, summary, files, params}]}))}` to be more machine-parseable, or register a structured output type.
• Add error classification to recovery hints. E.g., '429 (retryable, quota hit. Check https://convertica.net/pricing/); 401 (user-fixable, invalid or expired API key); 403 (possible plan limitation, ask user to verify subscription)'.
• Add idempotent and destructive hints to tool annotations if MCP SDK supports it. `convert_file` is idempotent (same input → same output), but `list_converters` is read-only. Explicit hints help agents reason about retry safety.
• Consider offering a `preview_conversion` dry-run mode (if the API supports it) to let agents test tool parameters without consuming quota.