cicash defines 5 tools with complete input schemas and descriptions. Naming follows verb_noun convention (budget_*). Descriptions are clear and action-oriented (avg ~120 chars), explaining WHAT, WHEN, and consequences. All parameters have types and descriptions. However, output schemas are not documented in the tool definitions, LLMs cannot predict return structure. Error handling is mentioned in budget_pay description but not formalized across tools. No parameter constraints (enums, ranges) despite opportunities (e.g., budget_delegate.per_tx should have min/max). Tool composition is excellent: each tool has one responsibility, and outputs chain naturally (quote → pay). Security is strong: credentials never exposed as parameters; wallet lives server-side.

• Document output schemas for all 5 tools. For budget_check, declare: {available: string, available_micro: number, max_per_tx: string, allowed_payees: [string], allowed_purposes: [string], expires_in_s: number, rate_limits: object, revoked: boolean, binding_owner: string}. For budget_quote, declare Quote structure (id, amount, payee, purpose, signature, etc.). For budget_pay, declare {paid: string, receipt_id: string, payee: string, purpose: string, remaining: string}.
• Add numeric constraints to budget_quote.amount and budget_delegate.budget/per_tx. E.g., amount: {type: number, minimum: 0.01, description: 'Amount in dollars (or microunits, clarify unit). Must be positive.'}. per_tx: {type: number, minimum: 0, description: 'Max per transaction in dollars. If omitted, defaults to budget value.'}.
• Formalize error responses. Define a standard error object: {error: string, action: 'RETRY_AFTER'|'REPLAN'|'ESCALATE', details?: object}. Document this in budget_pay and budget_quote descriptions. Include examples: 'If payee unknown, returns {error: "unknown payee", action: "REPLAN", known: [...]}'.
• Clarify budget_delegate.per_tx default. Add to description: 'If omitted, per_tx defaults to budget (no per-transaction limit). Set per_tx < budget to enforce tighter per-call bounds.'
• Specify amount units in budget_quote and budget_pay. Add to descriptions: 'Amount is in dollars (e.g., 10.50 for $10.50). Internally stored as microunits (cents × 100) but API accepts decimal dollars.' Ensure consistency with budget_check output (available_str vs available_micro).