Three tools with basic schemas and descriptions, but significant gaps in parameter documentation and error handling. Tool names lack action verbs (add, calculate, github-prs are weak). Descriptions are present but generic (10-60 chars, below the 50-200 char LLM-optimized baseline). Parameters have types but lack descriptions for most fields. The github-prs tool has a critical bug: githubToken is hardcoded to empty string, making the tool non-functional. No error recovery guidance. Output schemas are not documented. Composition is reasonable (three independent tools), but overall quality is below production baseline.

• Rename tools to verb_noun pattern: 'add' → 'add_numbers', 'calculate' → 'perform_arithmetic', 'github-prs' → 'search_github_prs'. This makes intent explicit and helps LLMs disambiguate.
• Add descriptions to all parameters. Example: 'a': 'First number to add (any real number)' and 'b': 'Second number to add (any real number)'. Descriptions should be 20-100 chars and explain the parameter's role.
• Fix github-prs: replace 'const githubToken = '';' with 'const githubToken = extra.env.GITHUB_PAT;' to actually read the environment variable. Validate that the token is present before making the API call.
• Document output schemas in tool descriptions. Example for add: 'Returns a text response containing the sum as a number string.' For github-prs: 'Returns an array of PR objects with fields: title (string), url (string), createdAt (ISO 8601 date), state (string: open|closed).'
• Enhance error messages with recovery guidance. Example: 'Error: GitHub PAT not found. Ensure GITHUB_PAT environment variable is set.' For API errors: 'Error fetching PRs: 403 Forbidden. Check that the GitHub token has read:public_repo scope and the username is valid.'