Two tools with minimal schemas and descriptions that lack actionable guidance. Both tools are discovery/reference tools (conventions, describe) with no parameters documented beyond optional type filtering. Descriptions are lengthy (200+ chars) but generic and repetitive, emphasizing copyright/licensing rather than usage patterns. No input parameter descriptions. No output schemas documented. No error handling guidance. Tool names lack action verbs (conventions, describe are weak; get_conventions, describe_surface would be clearer). No pagination, no structured output examples, no recovery paths.

• Rename tools to action verbs: 'get_conventions' and 'describe_surface_types'. This signals intent and disambiguates from similar discovery tools.
• Document output schemas for both tools. Show LLM what fields to expect (e.g., conventions returns {rules: string, citations: string, wiki_compounding: string}; describe returns {types: [{name, keys, filters}], schema: object}).
• Add description to 'type' parameter in describe: 'Optional PARA-ZK surface type (e.g., "projects", "areas", "resources", "archives"). Omit to list all available types.'
• Rewrite descriptions to focus on WHEN to call each tool and WHAT it enables, not copyright disclaimers. E.g., 'Call this FIRST to learn PARA-ZK conventions (ownership, citation format, wiki rules) before reading/writing notes.' and 'Call this to discover available surface types, stable keys, and collection filters for your vault.'
• Add error handling guidance: 'If CLI not found or vault unreachable, ensure Obsidian is running and CLI is on PATH. See install instructions: [link]. Retry after setup.'