Single tool with minimal definition quality. Tool name 'get_weather' follows verb_noun convention (+), but description is generic (18 chars, below 20-char threshold). Input schema present with basic structure but parameter 'city' lacks description entirely. No output schema documented. No error handling guidance. Tool definition inferred from file structure rather than explicit registration metadata visible in code. Fails multiple critical checks for production readiness.
Get the current weather for a given city.
Parameter 'city' has no description. LLMs cannot infer whether to pass 'New York', 'NYC', coordinates, or a city code.
Tool description is 18 characters ('Get the current weather for a given city.'), below the 20-char minimum and lacks context for LLM selection. Should explain WHEN to use this tool and what it returns.
No output schema documented. LLMs cannot plan downstream calls or extract temperature, conditions, or forecast data without knowing the response structure.
No error handling guidance. If city is not found or API fails, LLM receives no recovery hint (e.g., 'Try search_cities() first' or 'City not found, did you mean X?').
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 42 | <=2025-11-25 | v2 |
Tool definition inferred from file structure (tools/get_weather.js) rather than explicitly visible in registration code. Metadata and handler exports not shown in source; cannot verify schema completeness.