Four read-only query tools with basic schemas and minimal descriptions. All tools have input schemas with proper types and required flags, but descriptions are generic (10-30 chars) and lack context for LLM selection. Parameter descriptions are present but terse. No output schema documentation. No error handling guidance. Tools follow a repetitive pattern (query_by_X) but lack the depth expected for production use. Naming is clear but descriptions fail to explain WHEN to use each tool or what distinguishes them.

• Expand tool descriptions to 100-200 chars. Example: 'query_by_coordinate: Find all fish stocking records within a geographic bounding box (lat/lon range). Use this when the user specifies a location or map area. Returns species, location name, year, and exact coordinates.'
• Document output schema for all tools. Add to tool definition: 'Returns array of objects with fields: species (string), locationName (string), year (number), latitude (number), longitude (number).'
• Add range constraints to coordinate parameters: latMin/latMax must be -90 to 90; lonMin/lonMax must be -180 to 180. Include in parameter descriptions.
• Add error handling guidance: 'If no results found, suggest trying a broader coordinate range or different species. If coordinates are invalid, return: Invalid latitude: must be -90 to 90.'
• Implement pagination for large result sets. Add optional limit (default 50, max 500) and offset parameters. Document in tool description: 'Results are limited to 50 records; use offset to paginate.'