FastAPI-CRUD MCP exposes 5 CRUD tools with clear verb-noun naming (create_item, get_all_items, get_item, update_item, delete_item). All tools have descriptions (10 - 200 chars, within baseline range). Input schemas are present and properly typed with JSON Schema. However, parameter descriptions are minimal or missing context; output schemas are not explicitly documented; error handling lacks recovery guidance; and tool annotations (readOnlyHint, destructiveHint) are absent despite clear risk classifications in the metadata.

• Add tool annotations to FastApiMCP registration: mark create_item, update_item, delete_item with destructiveHint=true; mark get_all_items, get_item with readOnlyHint=true. This enables LLM safety reasoning without extra tool calls.
• Document output schemas in tool definitions: expose ItemOut schema (fields: id, name, description, created_at) and list response structure (items[], total_count, next_cursor). Include in tool description or via schema_ref.
• Enhance error messages with recovery guidance: change HTTPException(404, 'Item not found') to HTTPException(404, 'Item not found. Call get_all_items() to list available items or create_item() to add a new one.').
• Expand parameter descriptions with constraints: 'item_id (integer, 1 - 2147483647): The unique identifier of the item to retrieve.' Add 'skip' and 'limit' context: 'limit (1 - 100, default 10): Maximum items per page. Returns total_count for pagination.'
• Document idempotency and retry behavior: add to create_item and update_item descriptions: 'Idempotent: calling with identical input produces the same result. Safe to retry on transient failures.'

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

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