Two tools with basic schemas and descriptions, but significant gaps in parameter documentation and output specification. Tool names lack clear action verbs (weaviate-insert-one uses hyphenated format; weaviate-query is generic). Descriptions are minimal (10-30 chars) and lack context on when to use each tool or what they return. Parameter descriptions exist but are sparse. No documented output schemas, error handling guidance, or recovery paths. Missing idempotency hints for the write operation. No pagination support despite potential for large result sets.

• Expand tool descriptions to 100-200 chars. Include WHAT the tool does, WHEN to use it, and WHAT it returns. Example: 'Insert a single object into a Weaviate collection. Use this to add new records. Returns the UUID of the inserted object. Fails if the collection does not exist, call list_collections() first if unsure.'
• Document output schemas explicitly. For weaviate-insert-one, return {"id": "<uuid>", "success": true}. For weaviate-query, return {"results": [{"id": "<uuid>", "properties": {...}}], "count": <int>, "total": <int>}.
• Add pagination to weaviate-query: include 'limit' (default 20, max 100) and 'offset' (default 0) parameters. Return total count so LLMs know if more results exist.
• Rename tools to follow verb_noun convention: 'insert_object' and 'search_objects' (or 'query_objects'). Use underscores, not hyphens.
• Add error handling with recovery guidance. Return structured errors: {"error": "<message>", "code": "<code>", "suggestion": "<next step>"}. Example: 'Collection not found. Available collections: [...]'.