Tollbooth Authority is a domain-specific financial/cryptographic service with 6 tools. Most tools have descriptions and are registered via fastmcp, but the definitions lack rigor in several areas: (1) Input schemas are not visible in the provided code, tool registration is delegated to external wheel modules (tollbooth.authority and tollbooth.runtime), making schema validation impossible. (2) Tool names are verb-noun style (register_operator, purchase_credits, check_payment, check_balance, operator_status, certify_credits) which is acceptable, but descriptions vary widely in depth and actionability. (3) Parameter descriptions are minimal or absent in the visible code. (4) Output schemas are undocumented, no indication of what fields or structure each tool returns. (5) Error handling is not visible; recovery guidance is absent. The instructions in the FastMCP definition are comprehensive and educational, but tool-level definitions are thin. Since tool registration happens inside imported modules (AUTHORITY_TOOL_REGISTRY, register_authority_tools), the actual parameter schemas and return types are not visible in the provided source, forcing conservative scoring.

• Inline the tool registration code (or a representative excerpt) into server.py or provide a separate schema document showing full input and output definitions for all 6 tools. This is required to verify parameter types, descriptions, constraints (enums, min/max), and return field structures.
• For each tool, document the output schema explicitly. Example: 'register_operator returns {npub: string, balance_sats: integer}' or 'purchase_credits returns {invoice_id: string, checkoutLink: string, amount_sats: integer, expires_at: string (ISO 8601)}'.
• Add constraints to numeric parameters. Specify: purchase_credits amount_sats must be >= some minimum (e.g., 100 sats); certify_credits amount_sats must be > 0 and <= some max; invoice polling should have a timeout or max retry count.
• Document error scenarios for each tool with actionable recovery guidance. Example: 'check_payment returns invoice_pending (retry after 5 seconds), invoice_failed (balance not updated; try a different invoice), or settlement_timeout (contact support).' Structure errors as {error_code, message, recovery_action}.
• Add a dry_run or confirm_debit parameter to certify_credits. Before deducting the fee, allow the tool to return the computed fee and ask for confirmation. This prevents accidental over-deductions.
• Separate register_operator into idempotent discovery (get_operator_status if already registered) and creation (register_operator for first time) to clarify idempotency behavior.
• Document pagination for any list-like tools (if any). If operator_status or check_balance might return multiple entries, add limit and offset parameters.