Single tool 'markovian_notarize' has a strong, detailed description (287 chars) that explains what it does, when to use it, and key limitations. Input schema is present with two parameters (path, sha256), both typed and described. However, the schema lacks critical constraints: no enum for sha256 format validation, no minLength/maxLength for path, no pattern for sha256 hex validation. Output schema is completely undocumented, the tool returns a complex object with fields like 'leaf_index', 'inclusion_proof_url', 'witness_trust_policy' that are never formally specified. Error handling is minimal; the code catches exceptions but returns generic error strings rather than actionable recovery guidance. The tool name 'markovian_notarize' is clear and verb-based, but the description could better explain when to choose this over alternatives (if any exist). No pagination, no batch operations, no rate-limit guidance in the description despite the tool being rate-limited (10/hour).

• Document the complete output schema with all fields (leaf_index, inclusion_proof_url, witness_trust_policy, receipt, etc.), their types, and what they represent. Include example output.
• Add JSON Schema constraints to input parameters: sha256 pattern for hex validation, path minLength/maxLength, and additionalProperties: false is already correct.
• Enhance error messages with recovery guidance. E.g., 'Rate limit exceeded (10/hour). Retry after 3600 seconds.' or 'Invalid sha256 format. Expected 64 hex chars or sha256:HEXSTRING.'
• Return rate-limit metadata in responses (remaining_quota, reset_time) so agents can throttle multi-call sequences and avoid wasted calls.
• Add a 'dry_run' boolean parameter (default false) to preview the notarization without committing, enabling agents to validate before irreversible action.