Two tools with basic schemas and minimal descriptions. Both tools have input schemas with proper types (number, string, enum), but descriptions are extremely short (10-40 chars), falling well below the 50-200 char baseline for LLM-optimized descriptions. No output schema documentation. Error handling is minimal (divide-by-zero check in 'calculate' returns text, not structured error). Tool names lack action verbs ('add' and 'calculate' are weak; 'perform_addition' and 'perform_calculation' would be clearer). No parameter descriptions beyond type hints. Schemas are visible and properly typed, preventing a lower score, but the overall quality is below community median.

• Expand tool descriptions to 50-200 chars. Example: 'add' → 'Adds two numbers and returns the sum. Use when you need basic arithmetic addition. Returns a numeric result as text.'
• Add descriptions to all parameters. Example: 'a': 'First number to add (any real number)', 'b': 'Second number to add (any real number)', 'operation': 'Arithmetic operation to perform: add, subtract, multiply, or divide'.
• Document output schema explicitly in tool descriptions or via a separate schema field. Example: 'Returns {type: "text", content: string} with the numeric result or error message.'
• Rename tools with action verbs: 'add' → 'perform_addition', 'calculate' → 'perform_arithmetic_operation'.
• Return structured error responses with error codes and recovery hints. Example: {type: 'text', text: 'Error: division_by_zero. Cannot divide by zero. Provide non-zero divisor and retry.'}