Server has 21 well-named tools with consistent verb_noun patterns (get_, list_, download_). All tools have descriptions (10-100 chars, mostly 40-80 chars). Input schemas are present and properly typed with JSON Schema. However, parameter descriptions are sparse or missing entirely, most enum parameters lack explanatory text. Output schemas are not documented. Error handling is absent from visible code. No tool annotations (readOnlyHint, destructiveHint). All tools are READ_ONLY, which is good for safety but not explicitly declared in tool metadata.

• Add explicit descriptions to all enum and filter parameters. E.g., for 'status' in get_qonto_transactions: 'Filter by transaction status. pending=awaiting processing, completed=settled, declined=rejected, reversed=undone.'
• Document output schemas for all tools. Include field names, types, and what each field represents. E.g., get_qonto_organization should document that it returns {organization: {name, slug, bank_accounts: [{id, slug, currency, balance}]}}.
• Add tool annotations to all tools. Use readOnlyHint: true for all 21 tools to signal to agents that these are safe, non-destructive calls.
• Add min/max constraints and descriptions to pagination parameters. E.g., 'current_page: integer, minimum 1, default 1' and 'per_page: integer, minimum 1, maximum 100, default 20'.
• Add recovery hints to single-resource getters. E.g., get_qonto_transaction description: 'Get a single transaction by ID. If not found, try list_qonto_transactions with date filters to locate the transaction.'

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

• Relies on Dynamic Client Registration (deprecated) - use Client ID Metadata Documents (CIMD)