ToolCapsule exposes 2 tools with basic schemas and descriptions. Both tools have input schemas with required fields and property descriptions, meeting minimum structural requirements. However, descriptions are terse (create-doc: 62 chars, fetch-doc: 44 chars), parameter descriptions lack context about expected formats or constraints, and output schemas are entirely undocumented. Tool annotations (destructiveHint, readOnlyHint) are present but descriptions do not explain when to use each tool or what they return. No error handling guidance, no pagination support, and no composition hints. The mock server in tests/fixtures is a fixture, not production code, limiting confidence in actual implementation quality.

• Expand tool descriptions to 150 - 250 characters. For create-doc: 'Create a new document from Markdown content. Use this to generate reports, notes, or structured documents. For large payloads (>10MB), pass a local file path instead of inline markdown.' For fetch-doc: 'Retrieve an existing document by its ID or URL. Returns the full document content and metadata. Use this to read previously created documents or fetch external resources.'
• Add format/constraint descriptions to parameters. E.g., 'markdown: Markdown-formatted text (max 10MB; for larger content, use a file path)' and 'doc_id: Document identifier (UUID or URL; required)'.
• Document output schemas explicitly. E.g., create-doc returns {doc_id: string, created_at: ISO8601, url: string}; fetch-doc returns {doc_id: string, title: string, markdown: string, created_at: ISO8601}.
• Add error handling guidance in descriptions. E.g., 'If markdown is invalid, returns a validation error with line numbers. If doc_id does not exist, returns 404 with available document IDs.'
• Clarify tool composition. Ensure fetch-doc response includes doc_id so it can be passed to other tools; document any prerequisites or dependencies.