This repository was archived by the owner on Sep 4, 2025. It is now read-only.
- Notifications
You must be signed in to change notification settings - Fork 347
This repository was archived by the owner on Sep 4, 2025. It is now read-only.
[Tool Description] Improve Best Practices tool description for better LLM selection #820
Copy link
Copy link
Closed
microsoft/mcp
#106Description
Problem
The current Best Practices tool description lacks the detail and clarity needed for optimal LLM tool selection, resulting in an estimated confidence score of ~0.25 (well below target of ≥0.5).
Current Description Issues:
- Missing usage guidance (when to use vs when not to use)
- Vague purpose without specific context
- Limited scope explanation (only mentions SDK code generation)
- Poor parameter explanation
- Missing limitations/caveats
- Formatting issues (missing space after period)
- Too brief for the tool's importance
Current Description
Returns secure, production-grade Azure best practices. Call this before generating Azure SDK code.This tool is a hierarchical MCP command router. Sub commands are routed to MCP servers that require specific fields inside the "parameters" object. To invoke a command, set "command" and wrap its args in "parameters". Set "learn=true" to discover available sub commands.
Suggested Improvement
Returns secure, production-grade Azure best practices and recommendations for cloud architecture, security, performance, and cost optimization. Use this tool when you need guidance for Azure resource configuration, security hardening, deployment patterns, monitoring setup, or before generating Azure SDK code and infrastructure templates. This tool provides best practices for services like compute, storage, networking, databases, and security configurations. Do not use this tool for specific troubleshooting, resource management operations, or real-time monitoring - this tool focuses on providing architectural and security guidance rather than executing operations. This tool is a hierarchical MCP command router where sub-commands are routed to MCP servers that require specific fields inside the "parameters" object. To invoke a command, set "command" and wrap its arguments in "parameters". Set "learn=true" to discover available sub-commands for different Azure service areas and best practice categories.
Acceptance Criteria
- Update tool description to include comprehensive usage guidance
- Explain the broad scope of best practices covered
- Clarify when NOT to use this tool
- Detail the types of guidance provided
- Fix formatting issues
- Achieve confidence score ≥0.5 in tool selection testing
Related: Tool description review for improved LLM selection accuracy
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Done