Single tool 'add' has a valid schema with typed parameters (integers) but critical gaps in descriptions. Parameter descriptions are null/missing entirely, violating the baseline that 100% of A+ tools have parameter descriptions. Tool description is minimal (18 chars, below the 34-char p10 baseline). No output schema documented. No error handling guidance. No composition with other tools. The server also exposes prompts and resources but the evaluation focuses on the single tool.
Add two numbers
Parameter descriptions are null/missing. Input schema shows {"a":{"type":"integer","description":null},"b":{"type":"integer","description":null}}. Rubric requires every parameter to have a non-empty description explaining what it controls.
Tool description is only 18 characters ('Add two numbers'). Rubric baseline for p10 is 34 chars minimum. Descriptions under 20 chars cannot exceed 40 points. Needs context: WHEN to use this tool, WHAT it returns, any prerequisites.
No output schema documented. Rubric requires 100% of A+ tools to have documented return types. Agents cannot plan downstream calls or extract results without knowing the output structure.
No error handling or recovery guidance. If inputs are invalid (non-integer, overflow), the tool provides no actionable error message. Rubric requires errors to tell the LLM what to do next.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 36 | 2026-07-28+ | v2 |
Tool name 'add' lacks a clear verb_noun pattern. While 'add' is a verb, it is generic and does not convey the domain (e.g., 'add_numbers' would be clearer). Baseline shows 90% of A+ tools use explicit verb_noun naming.