15 tools with basic schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. All tools have names starting with action verbs (get_, create_, update_, delete_, list_, append_, search_) and descriptions present. However, most parameter descriptions are minimal (5-15 chars), and output schemas are not documented. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels. Error handling and recovery guidance absent. Schemas are present but sparse, many parameters lack type constraints, enums, or validation rules. Composition is reasonable (single responsibility per tool), but parameter relationships undocumented.
Append blocks to a Notion block's children
Create a comment on a Notion page or block
Create a new Notion database
Create a new Notion page
Delete a Notion block
Get a Notion block by ID
Get a comment by ID
Output schemas not documented. Tools return Notion API responses but LLMs cannot plan downstream calls without knowing response structure. E.g., get_page, query_database, search lack documented return types.
Parameter descriptions are minimal (5-15 chars). 'Properties to update' and 'Content to update' lack detail on format, required fields, or constraints. LLMs cannot infer valid input without richer descriptions.
No tool annotations despite clear risk levels. delete_block is DESTRUCTIVE, update_* are WRITE, get_* are READ_ONLY. Missing readOnlyHint, destructiveHint, idempotentHint annotations prevent agents from reasoning about safety and retry semantics.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 58 | <=2025-11-25 | v2 |
Get a Notion database by ID
Get a Notion page by ID
List a Notion block's children
Query a Notion database
Search for Notion objects
Update a Notion block's content
Update a Notion database
Update a Notion page's properties
No error handling or recovery guidance. Tools lack descriptions of failure modes, retryability, or next steps. E.g., 'page_id not found' should suggest search_pages() or list available pages.
Pagination parameters (start_cursor, page_size) present in query_database and list_blocks but no documentation of total count, next_cursor, or result limits. LLMs cannot plan multi-page iteration.