Two tools with minimal documentation. crypto-price has a basic description (47 chars) and a single required parameter with minimal context. fetch has a longer description (127 chars) but both tools lack parameter descriptions explaining format, constraints, or usage context. No output schemas are documented. Tool names lack action verbs (crypto-price should be get_crypto_price; fetch should be fetch_url). No error handling guidance, no pagination support, no idempotency markers. The plugin architecture via Extism WASM is innovative but tool definitions themselves are underdeveloped for LLM consumption.

• Rename tools with action verbs: crypto-price → get_crypto_price, fetch → fetch_url. Update tool registration in src/tools.rs.
• Add parameter descriptions: crypto-price.symbol should document valid formats (e.g., 'Bitcoin symbol or CoinGecko ID, case-insensitive, e.g. bitcoin, ethereum, cardano'); fetch.url should specify 'HTTP(S) URL to fetch, max 10MB response, 30s timeout'.
• Document output schemas in tool descriptions. E.g., crypto-price returns {price: number (USD), symbol: string, timestamp: ISO8601}; fetch returns {content: string (markdown), url: string, status: number}.
• Add error handling guidance: 'If symbol not found, try search_crypto_symbols() first' or 'If fetch fails with 404, the URL does not exist, verify with the user'.
• Implement response size limits and document them: 'fetch returns up to 50KB of content; larger pages are truncated. Use pagination or request specific sections.'

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

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