Loading ToolBench
Single tool 'add' has critical definition gaps. Tool name lacks action verb clarity (should be 'calculate_sum' or 'add_numbers'). Description is in Japanese ('足し算を実行する' = 'Perform addition'), 12 chars, below 20-char minimum. Both input parameters 'a' and 'b' have null descriptions, violating the requirement that every parameter must have a non-empty description. No output schema is documented. Tool is READ_ONLY, which is appropriate, but lacks error handling guidance. The Zod schema is present in code but parameter descriptions are completely absent.
足し算を実行する
Parameter descriptions are null for both 'a' and 'b'. LLMs cannot infer parameter meaning from names alone.
Tool description is 12 characters in Japanese ('足し算を実行する'). Descriptions under 20 chars cannot score above 0-20. Provide English description of 50-200 chars explaining what the tool does, when to use it, and what it returns.
Tool name 'add' lacks action verb prefix. Should be 'calculate_sum', 'add_numbers', or similar verb_noun pattern. Generic names reduce LLM clarity.
No output schema documented. LLMs need to know what fields to expect in the response to plan downstream calls and extract data correctly.
No error handling guidance. Tool should document what happens on invalid input (e.g., non-numeric values) and how to recover.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 32 | 2026-07-28+ | v2 |