All 5 tools have minimal descriptions (10-30 chars) and lack parameter descriptions entirely. Input schemas are present but parameters have no type annotations or descriptions. No output schemas documented. Error handling is basic (generic HTTP status errors). Tools follow a consistent naming pattern (verb_noun) but descriptions are too terse to guide LLM selection. No security considerations, no pagination support, no idempotency hints.

• Expand all tool descriptions to 50-200 characters. Example: 'last_pulse' → 'Retrieve the most recent NIST Randomness Beacon pulse (updated every 60 seconds). Returns pulse data including timestamp, output value, and cryptographic signature. Use this to get the latest random value without specifying a time.'
• Add descriptions to all parameters. Example: 'time_ms: Unix timestamp in milliseconds (e.g., 1716120000000). Must be within the last 30 days. If no pulse exists at this exact time, returns the nearest pulse.'
• Document output schemas for each tool. Example: 'last_pulse returns {pulse_index: number, time_ms: number, output: string (hex), signature: string, status_code: number}'.
• Enhance error handling with recovery guidance. Example: Instead of 'NIST Beacon: 404', return 'Pulse not found at time 1716120000000. Try pulse_at with a more recent timestamp, or call last_pulse to get the current pulse.'
• Add parameter constraints. Example: chain_id should be an enum or documented as 'integer 1-3 (NIST maintains 3 beacon chains)'. time_ms should document valid range (e.g., 'within last 30 days').