Two tools with minimal descriptions and incomplete schemas. get_query_data has a basic schema with one required parameter but lacks output documentation. get_dashboard_queries has an empty input schema (no parameters) and a trivial 8-character description. Neither tool documents return types, error conditions, or recovery guidance. Parameter descriptions are minimal. No tool annotations present. Naming follows verb_noun convention but descriptions fail to explain WHEN to use each tool or what data structure is returned.

• Expand get_dashboard_queries description to 50-150 chars explaining what it returns and when to call it first: 'Retrieve list of available Dune query IDs for the Pumpfun dashboard. Call this first to discover which queries are available before fetching data with get_query_data.'
• Document output schema for both tools. For get_query_data, specify: 'Returns object with fields: rows (array of result objects), columns (array of column metadata), execution_time (ms).' For get_dashboard_queries, specify: 'Returns array of objects, each with query_id (string) and description (string).'
• Add parameter constraint to query_id: 'Query ID as string (e.g., "3705945"). Discover valid IDs by calling get_dashboard_queries first. Invalid IDs return 404 error.'
• Add error handling documentation: 'Errors: 404 if query_id not found (call get_dashboard_queries to verify); 429 if rate limited (retry after 60s); 500 if Dune API unavailable (retry with exponential backoff).'
• Move DUNE_API_KEY to .env file only (never commit to source). Update package.json to include .env in .gitignore. Regenerate the exposed API key immediately in Dune dashboard.