Single tool 'modelroute_scan' has a basic description but critically lacks parameter descriptions and output schema documentation. The input schema defines only 'target' as a string with minimal context. No error handling guidance, no output structure documented, and no indication of what 'JSON findings' contains. The description is vague about the tool's actual purpose (is it a code scanner? a model router? both?). Naming is acceptable but descriptions fall far short of production standards.

• Add description to 'target' parameter: 'Filesystem path (relative or absolute) to scan for code quality issues. Can be a file or directory. If directory, recursively scans all files.'
• Document output schema in tool description: 'Returns JSON object with fields: tool (string), findings (array of {id, sev, where}), score (integer count of findings).'
• Clarify tool purpose: Is this a code scanner (TODO/FIXME detector) or a model routing proxy? Current description conflates two unrelated functions.
• Add error handling examples: 'If path not found, returns error with suggestion to verify path exists. If permission denied, returns error with required permissions.'
• Specify parameter constraints: 'target must be a valid filesystem path; max 4096 characters; relative paths resolved from current working directory.'