Loading ToolBench
Two tools with minimal but present schemas and descriptions. Both tools have basic verb-noun naming (getWikiDoc, getDocx) but descriptions are generic and lack context on when to use each vs. the other. Input schemas are visible and typed (string), but lack constraints, enums, or format guidance. No output schema documented. Error handling returns raw error strings without recovery guidance. No parameter validation rules stated. Tools lack idempotency hints, permission declarations, or audit trail guidance.
Retrieve the content of Feishu document directly
Retrieve the content of Feishu document from wiki space
No output schema documented. LLMs cannot plan downstream calls or extract structured data from responses. Both tools return {content: [{type: 'text', text: string}]} but this is not declared in tool definitions.
Descriptions lack context on when to use each tool. Both say 'Retrieve the content of Feishu document', unclear why two separate tools exist or which to call first. No dependency hints or disambiguation.
Error handling returns raw error strings ('Error: ' + err) without recovery guidance. LLMs cannot determine if errors are retryable, user-fixable, or fatal. No actionable next steps provided.
Parameter 'token' lacks format constraints. Description mentions 'often found in URL' but does not specify valid format, length, or character restrictions. LLMs may pass invalid tokens without validation.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 41 | <=2025-11-25 | v2 |
No tool annotations (readOnlyHint, idempotentHint). Both tools are read-only and idempotent, but this is not declared. Agents cannot optimize retry logic or understand safety properties.