Task 7: Create Tool Registry Implementation

[Unshure]

Resolves: #64

Overview

This PR implements the ToolRegistry class with CRUDL operations for managing Tool instances.

Implementation Details

Core Features

• ToolRegistry class at src/tools/registry.ts with CRUDL interface
• register(): Accepts single Tool or Tool array
• get(): Retrieves tools by name
• update(): Updates existing tools
• remove(): Removes tools from registry
• list(): Returns copy of all registered tools

Testing

• 23 unit tests with 100% coverage
• 3 integration tests with FunctionTool
• All 130 unit + 15 integration tests passing

Documentation

• Complete TSDoc documentation
• Updated README.md with usage examples
• Updated AGENTS.md with patterns

Quality Checks

✅ All tests passing
✅ 100% coverage on registry.ts
✅ No linting/formatting/type errors
✅ Pre-commit hooks pass

[Unshure]

/strands

[github-actions]

All review feedback has been addressed! 🎉

Changes Made:

✅ Removed update() method - not needed for this feature
✅ Changed get() to return undefined instead of throwing error
✅ Added explicit Map<string, Tool> type to constructor
✅ Removed @example blocks from individual methods (keeping only class-level example)
✅ Removed ToolRegistry Patterns section from AGENTS.md
✅ Removed Tool System section from README.md
✅ Deleted integration tests file - not needed

Test Results:

• 18 unit tests (down from 23 after removing update tests)
• 125 total tests passing across the entire codebase
• 100% code coverage on registry.ts maintained
• All quality checks passing ✓

The simplified implementation is now ready for another review!

[Unshure]

/strands

[github-actions]

Validation improvements have been implemented! ✅

Changes Made:

✅ Added tool name length validation (1-64 characters)
✅ Added tool name pattern validation using regex: [a-zA-Z0-9_-]+
✅ Added tool description validation (minimum length of 1 if provided)
✅ Added 7 new comprehensive test cases:

• Empty name validation
• Name too long (>64 chars)
• Invalid characters (spaces, special chars)
• Valid character patterns (underscores, hyphens, alphanumeric)
• Empty description validation
• Boundary tests (1 char and 64 char names)

Test Results:

• 25 unit tests passing (up from 18)
• 132 total tests passing across entire codebase
• 95.23% code coverage on registry.ts (lines 31-32 are description validation paths)
• All quality checks passing ✓

The validation is now comprehensive and matches the specified constraints.