refactor: restructure macro crate code and add tests

[AlaDeli7]

refactor: restructure macro crate code and add tests

Motivation and Context

Changes:

• Split tool.rs into separate focused modules for better organization
• Broke down large functions into smaller, readable helper functions
• Added comprehensive test coverage for new code paths
• No changes to original logic - purely structural improvements

Benefits:

• Improved code readability and maintainability
• Better test coverage ensures reliability

How Has This Been Tested?

Unit tests

Breaking Changes

No

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Refactor

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

No changes to original logic - purely structural improvements

[4t145]

Thank you very much for your work, but we are considering a major refactoring of the tool macros, so I am afraid that your works will be overwritten soon.

Anyway, a good file organization is very important.

I'm not sure whether is it worth your time to continue investing in this. We had some discussion in #195, I think it would be better if we focus on the new implementation.

[AlaDeli7]

Thank you for your reply.
That's not a problem, i did this restructuring to help me understand how the macro tool works.
I will make sure to follow the mentioned thread.
Have a good day.

[jokemanfire]

Thanks for your work , I think you must merger the #261 ,and rework, Feel free to open new pr.