Loading ToolBench
Generate Lorem Ipsum placeholder text on demand. Choose paragraphs, sentences, or words with exact count control.
Single tool 'text_generate_lorem_ipsum' has a well-structured schema with proper types and descriptions for both parameters (count, type). The tool description is comprehensive (280+ chars) and includes usage guidance, anti-patterns, and output format. However, the description embeds example output JSON and cross-references to non-existent tools (text_classify_content, text_convert_markdown_to_html, text_count_words), which violates the pattern of not including example values in descriptions and creates confusion about tool availability. Parameter descriptions are adequate but could be more precise about constraints (e.g., valid range for count, exact enum values for type). Output schema is documented in the description but not formally in JSON Schema format. No error handling guidance provided.
Use this when you need to generate placeholder text for mockups, wireframes, UI prototypes, or content templates. Returns Lorem Ipsum text with metadata. 1. text -- the generated Lorem Ipsum text 2. type -- what was generated (paragraphs, sentences, or words) 3. count -- how many units were generated 4. wordCount -- total word count of the generated text Example output: {"text":"Lorem ipsum dolor sit amet, consectetur adipiscing elit...","type":"paragraphs","count":3,"wordCount":150} Use this FOR populating design mockups, testing text rendering in UI components, or creating content placeholders during development. Use this BEFORE finalizing layouts to test text overflow and wrapping behavior. Do NOT use for text classification -- use text_classify_content instead. Do NOT use for markdown conversion -- use text_convert_markdown_to_html instead. Do NOT use for word counting -- use text_count_words instead.
Description includes example JSON output and references non-existent tools (text_classify_content, text_convert_markdown_to_html, text_count_words), violating the pattern of avoiding example values and creating false expectations about available tools.
Parameter 'type' lacks explicit enum constraint in schema; description states 'default: paragraphs' but schema does not enforce the three valid values (paragraphs, sentences, words) as an enum, allowing LLMs to pass invalid values.
Parameter 'count' lacks numeric bounds (min/max) in schema or description; no guidance on valid range, allowing LLMs to pass absurd values (0, negative, or millions) that may break the tool.
Output schema documented only in description text, not as formal JSON Schema; LLMs cannot parse the response structure programmatically, forcing manual parsing and increasing error likelihood.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 63 | 2025-06-18+ | v2 |
No error handling guidance; tool description does not explain what happens on invalid input (e.g., count=0, type='invalid'), preventing LLMs from self-correcting or understanding recovery paths.