Single tool with minimal definition quality. CPF Generator has a basic description (18 chars, below 20-char threshold) and input schema present but sparse. Parameter descriptions exist but are terse. No output schema documented. No error handling guidance. Tool name lacks action verb prefix (should be 'generate_cpf'). Overall definition falls well below production baseline of 194 chars for descriptions and lacks LLM-optimization patterns.

• Rename tool to 'generate_cpf' to follow verb_noun convention and improve LLM discoverability.
• Expand description to 50-150 chars: 'Generates a valid Brazilian CPF (Cadastro de Pessoas Físicas) number. Optionally specify a state to generate a CPF associated with that location. Returns formatted or unformatted string.'
• Document output schema explicitly: 'Returns a string containing the generated CPF (e.g., "12345678901" or "123.456.789-01" if formatted=true).'
• Convert 'state' parameter to an enum with all 27 valid Brazilian state codes (AC, AL, AP, etc.) from STATES_OPTIONS constant. Update description: 'Optional. Brazilian state code (AC, AL, AP, ...). If omitted, generates CPF for any state.'
• Add error handling note: 'If the external API is unavailable, the tool will return an error. Retry after a brief delay or inform the user that CPF generation is temporarily unavailable.'

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry