17 tools with inconsistent quality. All have descriptions (10-100+ chars) and basic schemas, but many lack parameter descriptions, enums for constrained inputs, and output documentation. OAuth/auth tools are well-named (get_request_token, get_access_token) but trading/portfolio tools lack clarity on return structures. No tool annotations (readOnlyHint/destructiveHint) despite clear risk levels. Error handling is absent from visible code. Naming follows verb_noun convention but some tools are vague (calculate_risk_parameters, view_portfolio). Parameter descriptions exist but are sparse, e.g., 'sortBy' in view_portfolio has no description of valid fields.

• Add output schemas to all tools. Document return type (object/array), field names, types, and descriptions. Example: get_account_balance returns {accountId: string, accountType: string, cash: {moneyMktBalance: number, ...}, computedBalance: {...}}.
• Add tool annotations: mark delete_alerts with destructiveHint=true, renew_access_token with idempotentHint=true, all read-only tools with readOnlyHint=true. This enables agents to reason about retry safety.
• Complete parameter descriptions. For 'sortBy' in view_portfolio, add 'Valid fields: symbol, quantity, price, gain_loss, gain_loss_pct'. For 'expiryType' in get_option_expire_dates, add enum constraint or valid values.
• Rename 'view_portfolio' to 'get_portfolio' and 'calculate_risk_parameters' to 'calculate_position_size' for clarity. Add descriptions explaining what each returns and when to use it.
• Add error handling to tool implementations. Return structured errors with recovery hints: {error: 'OAuth token expired', retryable: true, nextStep: 'Call renew_access_token() or get_request_token() to re-authenticate'}.