The server defines 3 tools with explicit registrations in src/index.ts. All tools have names, descriptions, and input schemas. However, there are significant gaps: (1) output schemas are not documented anywhere, LLMs cannot predict what these tools return; (2) parameter descriptions lack detail about format, constraints, and valid values; (3) no error handling guidance in descriptions; (4) descriptions are between 32 - 79 chars, below the 50 - 200 char LLM-optimized baseline; (5) no documentation of which parameters enable tool chaining (e.g., what fields the response includes). The tools are narrowly scoped and read-only (low risk), but the definitions lack production-grade precision.

• Add output schemas to all three tools. Document the JSON structure of get_record (fields returned for a feature/requirement), get_page (fields in a page object), and search_documents (result structure, pagination fields, total count). Example: 'Returns an object with {id, name, reference, status, description, ...}'
• Replace example values in parameter descriptions with formal constraints. For 'reference' in get_record and get_page, define: 'Reference number as a string matching the pattern [A-Z]+-[0-9]+ for features (e.g., DEVELOP-123) or [A-Z]+-[0-9]+-[0-9]+ for requirements (e.g., ADT-123-1)' and 'Reference number in the format [A-Z]+-N-[0-9]+ for pages (e.g., ABC-N-213)'. Add enum or pattern to the JSON Schema, not just the description.
• Expand tool descriptions to 100 - 150 chars and include: (a) what the tool does; (b) when to use it vs similar tools; (c) what it returns; (d) key parameters. Example for get_record: 'Fetch a specific Aha! feature or requirement by its reference number. Use this when you know the exact reference (e.g., DEVELOP-123). Returns the full record including status, description, and custom fields.'
• Add pagination support to search_documents. Document a 'limit' parameter (default 20, max 100), a 'page' or 'offset' parameter, and ensure the response includes 'total_count' and 'hasMore' fields. Prevent context window exhaustion.
• Document valid searchableType values. If only 'Page' is supported, remove the parameter or make it an enum with at least ['Page']. If other types exist (e.g., 'Feature', 'Requirement'), list them and explain what each returns.