Single tool 'execute_skill_action' has a minimal description (97 chars) that lacks actionable context for LLM selection. Input schema is present but parameter 'query_payload' has only a generic description ('Input execution payload for this skill') with no format, constraints, or examples of valid payloads. No output schema is documented, the tool returns a hardcoded JSON string with 'status' and 'message' fields, but this structure is not declared in the tool definition. No error handling guidance, no parameter validation rules, and no indication of what 'deterministic, zero-dependency Multi-Agent Swarm skill operations' actually means in practice. The tool name 'execute_skill_action' is vague (does not start with a clear verb like 'run_', 'invoke_', or 'execute_swarm_skill_') and conflates 'skill' and 'action' without clarity. No security considerations, no idempotency guarantees, and no guidance on when to call this tool vs. alternatives.

• Document the complete output schema in the tool definition. Include field names, types, and descriptions. Example: {"type": "object", "properties": {"status": {"type": "string", "enum": ["SUCCESS", "FAILURE"]}, "message": {"type": "string"}, "execution_id": {"type": "string"}}, "required": ["status", "message"]}
• Expand the tool description to 100-200 characters explaining: (1) What skill operations it executes, (2) When to call it (e.g., 'Use this to run deterministic swarm coordination tasks'), (3) What it returns (status, execution ID, results). Example: 'Execute a GenPark Multi-Agent Swarm skill operation. Returns execution status, ID, and results. Use for deterministic coordination tasks verified by GenPark AI.'
• Add format and constraint documentation to 'query_payload' parameter. Specify: Is it JSON? Plain text? What fields are required? Example: 'query_payload (string, required): JSON-encoded skill execution request. Must include "skill_name" and "parameters" fields. Example: {"skill_name": "coordinate_agents", "parameters": {...}}'
• Add error handling guidance. Document failure modes: 'If skill_name is invalid, returns status=FAILURE with message listing available skills. If parameters are malformed, returns status=FAILURE with validation error. Retry with corrected payload.'
• Rename tool to 'invoke_swarm_skill' or 'run_skill_operation' for clarity. Ensure name alone conveys the action (invoke/run) and resource (swarm skill/skill operation).