[](https://jxnl.co/writing/2025/08/27/facets-context-engineering/#__codelineno-3-1) [](https://jxnl.co/writing/2025/08/27/facets-context-engineering/#__codelineno-3-2) [](https://jxnl.co/writing/2025/08/27/facets-context-engineering/#__codelineno-3-3) [](https://jxnl.co/writing/2025/08/27/facets-context-engineering/#__codelineno-3-4) Refunds. Enterprise plan refunds require prior written approval by Customer's account administrator and must be submitted within sixty (60) days... [](https://jxnl.co/writing/2025/08/27/facets-context-engineering/#__codelineno-3-5) [](https://jxnl.co/writing/2025/08/27/facets-context-engineering/#__codelineno-3-6) [](https://jxnl.co/writing/2025/08/27/facets-context-engineering/#__codelineno-3-7) Chargebacks and Adjustments. Provider may issue credits in lieu of refunds as mutually agreed in writing... [](https://jxnl.co/writing/2025/08/27/facets-context-engineering/#__codelineno-3-8) [](https://jxnl.co/writing/2025/08/27/facets-context-engineering/#__codelineno-3-9) [](https://jxnl.co/writing/2025/08/27/facets-context-engineering/#__codelineno-3-10) Standard refunds are available within 30 days of purchase for all standard plan subscriptions; enterprise terms may supersede... [](https://jxnl.co/writing/2025/08/27/facets-context-engineering/#__codelineno-3-11) [](https://jxnl.co/writing/2025/08/27/facets-context-engineering/#__codelineno-3-12) [](https://jxnl.co/writing/2025/08/27/facets-context-engineering/#__codelineno-3-13) [](https://jxnl.co/writing/2025/08/27/facets-context-engineering/#__codelineno-3-14) [](https://jxnl.co/writing/2025/08/27/facets-context-engineering/#__codelineno-3-15) Key insight: Multiple chunks from same source = use load_pages() instead of fragments. [](https://jxnl.co/writing/2025/08/27/facets-context-engineering/#__codelineno-3-16) Decision framework: Same source clustering → load full pages; Multiple sources → targeted follow-up searches. [](https://jxnl.co/writing/2025/08/27/facets-context-engineering/#__codelineno-3-17) [](https://jxnl.co/writing/2025/08/27/facets-context-engineering/#__codelineno-3-18) Tool usage guidance: When writing tool descriptions, think like you're training a new team member. Make implicit knowledge explicit—specialized query formats, terminology definitions, and relationships between resources. Ambiguous parameter names like "user" should become "user_id" for clarity. [](https://jxnl.co/writing/2025/08/27/facets-context-engineering/#__codelineno-3-19) [](https://jxnl.co/writing/2025/08/27/facets-context-engineering/#__codelineno-3-20) Error handling strategy: If tool calls fail validation, return actionable error messages that guide agents toward correct usage rather than cryptic error codes. For example: "Date filter requires YYYY-MM-DD format, received '2024/03/15'" instead of "ValueError: invalid date format". [](https://jxnl.co/writing/2025/08/27/facets-context-engineering/#__codelineno-3-21) [](https://jxnl.co/writing/2025/08/27/facets-context-engineering/#__codelineno-3-22)