Two well-named, read-only tools with strong descriptions (190 - 280 chars each) and complete input schemas. Both tools follow verb_noun naming (hts_search, hts_lookup) and clearly state their purpose and when to use them. Input parameters are typed and described. However, output schemas are not formally documented in the tool definitions, the code shows what is returned (shaped entries, provisions, error objects) but the tool definitions lack explicit outputSchema declarations. Error handling is present but minimal (basic error messages without recovery guidance). No tool annotations (readOnlyHint, idempotentHint) despite both being read-only and idempotent.

• Add explicit outputSchema to both tool definitions documenting the structure of results (e.g., for hts_search: array of {hts_code, description, indent, general_rate, special_rate, column2_rate, units, section_301_232_refs}; for hts_lookup: {hts_code, base, provisions, effective_note}).
• Add readOnlyHint: true and idempotentHint: true to both tool definitions to signal to agents that these calls are safe to retry and do not modify state.
• Enhance error messages with recovery guidance: 'No HTS line found for "8712.00.48". Try a broader product keyword like "bicycles" or "electric bicycles".' and 'Required argument "query" is missing. Provide a product description (e.g., "lithium batteries") or an HTS code (e.g., "8712.00.48").'
• Document the limit parameter range explicitly: 'Max tariff lines to return (1 - 50, default 15). Results are sorted by relevance; use hts_lookup for a specific code.'
• Add a note to hts_search description about pagination: 'If results are truncated, increase limit or refine your query. For the effective total duty including Section 301/232 add-ons, pass the exact HTS code to hts_lookup.'