Two tools with basic schemas and minimal descriptions. analyze_project_structure has a proper input schema with typed parameters and descriptions, but get_toolkit_version lacks parameter descriptions (empty properties object). Both tool descriptions are under 100 chars and lack context on WHEN to use them or WHAT they return. No output schemas documented. No error handling guidance. No parameter constraints (e.g., max_depth bounds). Naming is acceptable (verb_noun pattern) but descriptions are too terse to guide LLM selection effectively.

• Expand tool descriptions to 100-200 chars. For analyze_project_structure: 'Recursively scans a directory tree and returns structure (directories and files) up to a specified depth. Use this to understand project layout before analyzing code. Returns a dict mapping paths to {directories, files}.'
• Document output schemas explicitly. Add to tool definitions: 'Returns: {"type": "object", "properties": {"<path>": {"type": "object", "properties": {"directories": ["string"], "files": ["string"]}}}'
• Add parameter constraints. For max_depth, update description to: 'Maximum depth for directory traversal (1-10, default: 2). Prevents excessive scanning of deep trees.'
• Implement actionable error messages. When path does not exist, return: 'Path does not exist. Verify the path is absolute or relative to the working directory. Available parent directories: [list]'
• Add tool annotations to schema. Include 'readOnlyHint': true and 'idempotentHint': true in tool definitions to signal safety to agents.