Refactor unit tests to avoid hard-coded description string checks for tools

[anannya03]

Several unit tests across the MCP Tools codebase (e.g., UpdateWorkbooksCommandTests, UpdateAlertsCommandTests, etc.) currently assert that tool descriptions or summaries exactly match hard-coded strings. These tests frequently fail when a description is reworded or improved for clarity, even though the tool’s behavior remains correct.

To improve long-term maintainability and reduce noise in CI, we should refactor these tests to avoid strict string matching. Instead, they should focus on verifying functional correctness and required metadata.

Such testcases should be improved.