BICE CLI exposes 8 banking tools via HTTP REST API. All tools have basic descriptions (10-100 chars), but parameter schemas are severely incomplete. Most tools lack input schema definitions entirely, only get_transactions, get_monthly_summary, get_portfolios_summary, and get_movements declare parameters. No output schemas are documented. Descriptions are generic and lack context for LLM selection (e.g., 'Fetches user information' does not explain when to call get_user vs get_whoami). Parameter descriptions exist but are minimal. No error handling guidance, no idempotency hints, no permission scopes. Tool names follow verb_noun convention (positive), but composition is weak, no chaining IDs returned, no pagination metadata. Security: credentials appear to be loaded server-side (loadConfig), which is correct, but no audit logging visible.

• Add explicit input schemas to all 8 tools. For get_user, get_whoami, get_products, get_balance: declare required/optional params (e.g., product_id if filtering). Use JSON Schema with type, description, and constraints.
• Document output schemas for all tools. Example: get_transactions should return {transactions: [{id, date, amount, description}], total_count, page, limit}. This enables LLMs to chain calls (e.g., extract transaction_id for detail lookup).
• Expand descriptions to 50-150 chars. Example: 'Fetches current user profile (name, email, account status). Call this to verify login or get user metadata before accessing products.' Distinguish get_user (profile) from get_whoami (session + linked accounts).
• Add type and constraint info to parameters. Change 'page' and 'limit' from string to integer with min/max (page: 1-999, limit: 1-100). Add enum for 'month' in get_movements (january|february|...|december).
• Add error handling guidance in descriptions. Example: 'Returns 401 if session expired (call login command). Returns 404 if product not found (call get_products to list available). Returns 500 on server error (retry after 5s).' Include recovery paths.