Single tool with basic schema and minimal descriptions. Tool name 'write_note' follows verb_noun convention (+), but description is only 19 characters, below the 20-char minimum threshold. Input schema present with proper JSON Schema structure, but parameter descriptions are generic and lack actionable constraints. No output schema documented. No error recovery guidance. No tool annotations (readOnlyHint/destructiveHint). Missing idempotency guarantees for a write operation.
Write note to inBox
Tool description is only 19 characters ('Write note to inBox'), below 20-char minimum. Lacks context on when to use, what it returns, and prerequisites.
No output schema documented. LLM cannot predict response structure or plan downstream operations. Actual response includes 'content' array with 'type' and 'text' fields, but this is not declared in tool definition.
Parameter descriptions lack actionable constraints. 'Optional title of the note' and 'Text content of the note with markdown format' do not specify length limits, format requirements, or character restrictions. Code enforces 3000-char limit but this is not documented in schema.
No tool annotations. Tool performs a destructive write operation but lacks destructiveHint annotation. LLM cannot determine if operation is safe to retry or has irreversible consequences.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 44 | 2026-07-28+ | v2 |
Error handling lacks recovery guidance. Errors like 'Content is required' and 'inBox token or URL not set' are present but do not guide LLM on next steps (e.g., 'Provide content parameter' or 'Set INBOX_USER_TOKEN environment variable').