Loading ToolBench
Single tool with minimal definition quality. Tool name 'create_new_project' follows verb_noun convention (+), but description is only 34 chars, below the 50-char minimum for actionable guidance. Input schema present but lacks parameter description (only 'Project name.' is provided). No output schema documented. No error handling guidance beyond raw HTTP status codes. No parameter constraints (enum, pattern, length). Tool does not indicate it modifies state (WRITE risk) in description. Missing: pagination, idempotency guidance, recovery paths, and structured output specification.
Create a new OpenShift project request.
Description too short (34 chars). Must explain WHAT the tool does, WHEN to use it, and what it returns. Current text 'Create a new OpenShift project request.' lacks context for LLM selection.
No output schema documented. LLM cannot infer what fields to expect from the response. Currently returns raw string ('Success' or error message), not structured JSON.
Parameter 'project' lacks description in schema. Only tool docstring mentions 'Project name.', schema must include description field for LLM clarity.
No error handling guidance. Errors return raw HTTP status codes and response text (e.g., 'Error: 400 - ...'). LLM cannot determine if error is retryable, user-fixable, or fatal.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 37 | 2026-07-28+ | v2 |
No input validation or constraints. Parameter 'project' accepts any string; no length limits, character restrictions, or naming rules documented. LLM may pass invalid project names.