Diariz has a single MCP tool (add_as_attachment) with a clear, well-structured definition. The tool name follows verb_noun convention (add_as_attachment), has a substantive description (178 chars), proper input schema with typed parameters, and documented descriptions for each parameter. However, the server offers only ONE tool, which limits its utility as a general MCP integration. The tool is write-only (RISK: WRITE) with no error handling guidance, no recovery suggestions, and no pagination (not applicable here but indicates limited sophistication). The schema is well-formed with type=object, required fields, and parameter descriptions, meeting baseline standards for a simple operation. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) are present despite the destructive nature of the operation.

• Add tool annotations: set destructiveHint=true (or equivalent) to signal to the MCP client that this modifies state. Optionally add idempotentHint if retries are safe.
• Enhance error handling in description: 'If the transcript is not found or markdown is invalid, the call returns an error. Ensure the transcript context is set before calling this tool.'
• Document idempotency: 'Calling this tool multiple times with the same name and content will replace the previous attachment, not duplicate it.' This guides agent retry logic.
• Add constraints to 'name' parameter: specify max length (e.g., 255 chars), allowed characters (alphanumeric, hyphens, underscores), and clarify collision behavior.
• Expand MCP surface: add tools like list_transcripts, get_transcript, search_transcripts, update_attachment, delete_attachment to make the server a full transcript-management interface.
• Add output schema documentation: describe what the tool returns on success (e.g., {attachment_id, transcript_id, created_at}) so agents can chain further operations.
• Document prerequisites: 'Requires an active transcript context. If multiple transcripts are selected, the user will be prompted to choose one.'