Single tool 'query_table' has a minimal schema with only a 'prompt' parameter (string, no constraints). Tool description is generic and does not explain WHAT queries are supported, WHEN to use it, or what the output structure is. No output schema documented. Parameter lacks format/constraint guidance. No error handling patterns visible. Tool appears to convert natural language to DynamoDB queries via OpenAI, but this critical behavior is not stated in the description. Schema is present but trivial; descriptions are under 100 chars and lack actionable detail.

• Expand tool description to 100-200 chars: 'Search and filter records in DynamoDB tables using natural language. Supports filtering, sorting, limiting, and counting. Returns matching records with specified fields. Use this to query configured tables without writing SQL or DynamoDB syntax.'
• Document the output schema in the tool definition: { type: 'object', properties: { result: { type: 'string', enum: ['OK', 'error'] }, tableName: { type: 'string' }, records: { type: 'array', items: { type: 'object' } }, count: { type: 'integer' }, errorMessage: { type: 'string' } } }
• Add constraints to the 'prompt' parameter: description should state 'Natural language query (e.g., "Find all users with status=active and created after 2024-01-01"). Supports filtering, sorting, limiting, and counting. Max 500 characters.'
• Add error handling examples in the tool description or a separate error_handling field: 'If OpenAI API fails, returns {result: "error", errorMessage: "OpenAI service unavailable. Retry in 30 seconds."}. If table not found, returns {result: "error", errorMessage: "Table not found. Available tables: [list]"}.'
• Rename tool to 'search_dynamodb_table' or 'filter_dynamodb_records' to clarify the action and distinguish from other potential DynamoDB tools (e.g., get_item, put_item).