Three tools with minimal parameter schemas and inconsistent description quality. No tools document output schemas. No error handling guidance. No tool annotations. Naming is clear (verb_noun pattern), but parameter documentation is absent.

• Add explicit input schemas to all tools. Even empty-parameter tools should declare Input: {} with a description field explaining why no parameters are needed. For OAuth tools, document that no user input is required, the browser flow handles authentication.
• Document output schemas for each tool. E.g., list_books returns {type: 'array', items: {type: 'object', properties: {id, title, author, ...}}}. get_my_books returns {type: 'object', properties: {user: string, books: array, total: number, page: object, _links: object}}.
• Remove test credentials and implementation details from descriptions. Replace 'alice (password: alice123)' with 'This tool opens your browser for OAuth login, no credentials pass through Claude.' Keep descriptions under 200 chars and focused on intent.
• Add error handling guidance. E.g., 'If authorization times out after 2 minutes, the user may have closed the browser tab. Suggest they try again.' Return structured error objects with 'error_type' (timeout|cancelled|network) and 'recovery_hint' fields.
• Add tool annotations to the FastMCP decorator. Mark all three tools with readOnlyHint=true and idempotentHint=true so agents know they are safe to retry and do not modify state.