Single tool 'convert' has a clear verb-noun name and complete input schema with proper type constraints (base 2-36). Description is adequate (97 chars) but lacks context on when to use it or what it returns. Parameter descriptions are minimal: 'from_base' and 'to_base' lack any explanation of what they represent. Output schema is not documented, LLMs cannot predict the ConvertResult structure (input, from_base, to_base, decimal, result fields). Error handling returns plain text messages without recovery guidance. No tool annotations (readOnlyHint, idempotentHint) despite being a pure read-only, idempotent operation.

• Add descriptions to 'from_base' and 'to_base' parameters explaining they are radix values (2-36) and giving examples (2=binary, 10=decimal, 16=hex).
• Document the output schema in the tool description: 'Returns an object with fields: input (original string), from_base, to_base, decimal (base-10 representation), result (converted string in target base).'
• Expand tool description to ~150-200 chars: explain use cases (binary↔hex conversion, arbitrary precision), mention that negative numbers are preserved, and clarify the output structure.
• Add readOnlyHint: true and idempotentHint: true to the tool definition to signal safety to agents.
• Improve error messages with actionable recovery hints: 'Invalid base: must be 2-36' instead of 'base must be in [2, 36]'; 'Invalid digit for base X: valid characters are 0-9, a-z' instead of generic 'invalid digit'.