Server provides 8 read-only tools with consistent naming (verb_noun pattern: get_, list_, search_) and basic descriptions. All tools have input schemas with type definitions. However, descriptions are generic (avg ~60 chars, below 194-char baseline), parameter descriptions lack detail about constraints/formats, and output schemas are not documented. No error handling guidance, no pagination support despite list_rules potentially returning many items, and no tool annotations (readOnlyHint). Composition is sound, each tool has one responsibility, but descriptions don't explain WHEN to use each tool vs. alternatives (e.g., get_rule vs. search_rules).

• Expand tool descriptions to 100 - 200 chars. Include WHEN to use each tool: 'Use get_rule to retrieve a single rule by exact name/ID/alias. Use search_rules to find rules matching keywords when you don't know the exact name. Use get_rules_for_task to get recommended rules for a development context.'
• Document parameter constraints in descriptions. E.g., 'rule_name (string): The exact name, ID, or alias of the rule. Valid aliases are listed in list_rules output. Case-sensitive.'
• Add output schema documentation as JSDoc comments or in tool descriptions. E.g., 'Returns {id: string, title: string, aliases: string[], content: string, kind: "rule"|"learning"|"index"}'
• Add pagination to list_rules: accept optional limit (default 20, max 100) and offset parameters; return {rules: [...], total: number, offset: number}.
• Add readOnlyHint: true annotation to all 8 tools in the tool definition to signal they are safe to cache and retry.