Single tool with minimal schema and generic description. Input schema present but lacks parameter descriptions. Tool description is adequate (89 chars) but parameter 'request' has no description in the schema itself. No output schema documented. No error handling guidance. No tool annotations. Composition is monolithic, the tool attempts to resolve capabilities into 'exact documented capability items' but the mechanism is opaque to the LLM.

• Add description to 'request' parameter in schema: 'The complete user request, including all dependent steps and context needed to resolve required capabilities. Example: "List all available commands for managing users and then show how to create a new user."'
• Document output schema with example: 'Returns {capabilities: [{name, description, type}], plan: string, notes: string}' so LLM knows what to extract.
• Add error handling guidance: 'If request is ambiguous, return {error: "ambiguous_request", suggestion: "Please clarify..."}' with recovery hints.
• Rename tool to 'resolve_required_capabilities' or 'map_request_to_capabilities' to clarify that it maps user intent to a capability catalog.
• Add tool annotations: mark as readOnlyHint=true and idempotentHint=true since it never executes capabilities, only resolves them.