39 tools with consistent naming (verb_noun pattern) and descriptions present. However, critical gaps: (1) Most parameter descriptions are minimal (5-15 chars), violating the 72-char baseline for param annotations. (2) Output schemas are not documented, LLMs cannot infer response structure. (3) No error handling guidance; tools return raw API errors without recovery hints. (4) Sensitive operations (groupme_destroy_bot, groupme_remove_member) lack confirmation/dry-run patterns. (5) Tool descriptions average ~60 chars, below the 194-char baseline; many lack WHEN/WHY context. Example: 'groupme_login' description is 'Registers a GroupMe access token for the authenticated user' (60 chars), missing prerequisites, error cases, or what happens if token is invalid.

• Document output schemas for all tools. Example: 'Returns {groups: [{id, name, member_count, created_at}], total_count: int}'. This enables LLMs to chain tools and extract required IDs.
• Expand parameter descriptions to 50-100 chars with format/range constraints. Example: 'Numeric group ID (1-999999999)' → 'Numeric group ID (1-999999999). Use groupme_list_groups to discover IDs if you only have a group name.'
• Add confirmation/dry-run support to destructive tools (destroy_bot, remove_member). Return a confirmation_token and require it in a separate confirm_* call, or add a 'dry_run' parameter.
• Enrich error responses with recovery guidance. Catch API errors and return: '{error: "User not found", suggestion: "Try groupme_search_groups() with a partial name", retryable: false}'.
• Expand tool descriptions to 100-150 chars. Include WHEN to use, prerequisites, and common next steps. Example: 'Sends a message to a group. Use groupme_list_groups first if you only have a group name. Supports text and attachments (images, files). Rate limit: 5 msgs/sec per group.'

Inferred effective spec: 2026-07-28+.

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