Both tools have minimal descriptions (under 100 chars) and critically lack input parameter descriptions. Tool 1 (get_available_entity_sets) has an empty input schema with no parameters documented. Tool 2 (call_specific_bc_entity) has one parameter ('Entity Name') with a description, but lacks type constraints, enums, or validation guidance. Neither tool documents output schemas. No error handling guidance, no pagination support despite likely returning lists, and no security/permission documentation. The server uses HTTP transport (positive), but tool definitions fall well below production baseline (194 chars avg description, 100% of A+ tools have param descriptions).

• Add comprehensive output schema documentation for both tools. Specify fields returned (e.g., entity_set_name, entity_type, description, odata_type) with types and descriptions.
• Expand Tool 1 description to 150-200 chars: 'Retrieves the list of available Business Central entity sets (e.g., employees, customers, vendors). Call this first to discover which entities you can query. Returns entity names and metadata for selection.'
• For Tool 2, add enum constraint or validation rule for 'Entity Name' parameter. Document valid entity names or a pattern (e.g., 'lowercase alphanumeric, e.g., employees, sales_orders'). Add description: 'The Business Central entity to query (e.g., employees, customers, vendors). Must match an entity from get_available_entity_sets.'
• Add error handling guidance: 'If entity not found, call get_available_entity_sets() to list valid entities. If BC API returns 401, verify credentials in configuration.'
• Document pagination: if results can exceed 50 items, add limit and offset/skip parameters. Return total_count and next_offset to enable LLM-driven pagination.