Binnacle has 10 tools with clear verb-noun naming (list_tree, get_page, create_page, etc.) and consistent descriptions. All tools have input schemas with typed parameters and descriptions. However, descriptions are terse (10-50 chars), lacking context on WHEN to use each tool or what downstream actions they enable. Output schemas are not documented, LLMs cannot predict response structure for chaining. Error handling is minimal; no recovery guidance. Parameter descriptions lack constraints (e.g., no max length for title, no HTML validation rules). Missing tool annotations (readOnlyHint, destructiveHint) despite clear risk levels in metadata.

• Document output schemas for all tools. E.g., 'Returns {tree: [{id, title, parent_id, children: [...]}], total: N}' for list_tree. Include field types and whether pagination is supported.
• Expand descriptions to 50 - 150 chars with context. E.g., 'Get a single page by ID or path. Use this to fetch content for display or editing. Returns title, HTML body, version, and parent_id for navigation.'
• Add tool annotations to worker.ts tool registration. Map risk levels to MCP hints: READ_ONLY → readOnlyHint=true, DESTRUCTIVE → destructiveHint=true, REVERSIBLE → idempotentHint=true.
• Add parameter constraints in descriptions. E.g., 'page title (required, 1 - 255 chars, no HTML tags)' and 'URL slug (optional, alphanumeric + hyphens, auto-generated if omitted)'.
• Add error recovery guidance. E.g., delete_page: 'If the page has children, move them to a new parent first, then delete. Returns error code CHILDREN_EXIST with child count if applicable.'

Inferred effective spec: <=2025-11-25.

• Relies on Dynamic Client Registration (deprecated) - use Client ID Metadata Documents (CIMD)