Four tools with minimal but present descriptions (10-50 chars each). All tools have basic input schemas with type and description for parameters. Naming follows verb_noun pattern (wiki_pages_get, tracker_issues_get, forms_surveys_get, status_check). However, descriptions are below the 50-200 char LLM-optimized baseline (rubric: avg 194 chars). No output schemas documented. No error handling guidance. Tool annotations present (readOnlyHint via Risk field). Composition is sound, each tool does one thing. Missing: pagination info, return field documentation, recovery guidance for failures.

• Expand tool descriptions to 50-200 chars. Example: 'wiki_pages_get: Retrieve a single wiki page by its slug. Returns page content, metadata (created_at, updated_by), and attachment list. Use this after search_wiki_pages() to fetch full page details. Returns 404 if slug not found.'
• Document output schemas for all tools. Specify which fields are returned (e.g., page_id, title, content, created_at, updated_by, attachments). This enables LLMs to chain tools and extract required IDs.
• Add error recovery hints to descriptions. E.g., 'If slug not found, call search_wiki_pages(query=<partial_name>) to discover available pages.' This guides LLM self-correction.
• Enhance parameter descriptions with format constraints. E.g., 'slug: Page slug identifier (lowercase alphanumeric + hyphens, max 100 chars, e.g., my-page-title)', but use enum or pattern in schema, not example values in text.
• Add pagination guidance if tools return large results. Specify: 'Results are limited to 50 items. Use limit and offset parameters to paginate. Returns total_count for planning.'

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

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