FAS MCP provides 4 well-named, read-only agricultural data tools with complete input schemas and reasonable descriptions. All tools follow verb_noun naming (fas_exports, fas_imports, fas_production, fas_commodity_codes). Schemas include type definitions and required fields. However, output schemas are entirely undocumented, LLMs cannot predict response structure or plan downstream calls. Parameter descriptions lack format constraints (e.g., year format, country code format). Error handling is present but generic. No tool annotations (readOnlyHint, etc.). Missing pagination guidance for potentially large result sets.

• Document output schemas for all tools. Example for fas_exports: 'Returns {exports: [{year: string, commodity: string, destination: string, volume: number, value: number}], total_count: number}'.
• Add format constraints to year and country parameters. E.g., 'start_year: Start year in YYYY format (e.g., 2020). Must be 1990 - 2024.' and 'country: ISO 3166-1 alpha-2 country code (e.g., CN, MX, JP).'
• Add pagination guidance: 'Results are limited to 100 records. Use market_year to narrow results. For historical data spanning multiple years, call the tool once per year.'
• Add readOnlyHint: true to all tool definitions to signal to agents that these tools are safe to call without side effects.
• Enhance error recovery: Instead of 'use NASS Quick Stats', return 'FAS API unavailable. Try: (1) search_usda_nass(commodity, year) for US production, or (2) check https://apps.fas.usda.gov/psdonline manually.'