Five tools with mixed quality. search_law, lookup_naics, and format_checklist have reasonable descriptions (40-80 chars) and basic schemas, but lack parameter descriptions and output schema documentation. finalize_handoff and formation.handoff have enums and contact fields but no output schema docs. No tool has error handling guidance, recovery hints, or idempotency markers. Parameter descriptions are sparse or missing entirely (e.g., 'limit' in search_law lacks range/default guidance). No tool documents what it returns or how to chain results to downstream tools. Naming is verb-forward (search_, lookup_, format_, finalize_) but descriptions don't explain WHEN to use each tool vs. alternatives.

• Document output schema for each tool. E.g., search_law returns {results: [{citation: string, excerpt: string, url: string}], total: number, next_cursor?: string}. This enables chaining and context planning.
• Add parameter descriptions with constraints: search_law.limit should be '1-50 results per page (default 6)'; jurisdiction should be '2-letter state code (MS, CA) or city code (CA-SF)'.
• Add error recovery hints: 'If jurisdiction not found, try search_law with a broader query or check supported jurisdictions at corpuslaw.us/jurisdictions'.
• Consolidate finalize_handoff and formation.handoff into a single tool with consistent parameter names (use 'state' everywhere, not 'jurisdiction'). Document when to call it (after user confirms entity type and state).
• Add idempotency markers and dry-run support to write tools. E.g., finalize_handoff should accept a 'dry_run' parameter to validate without creating a handoff URL, or document that repeated calls with identical inputs return the same URL.