KeyProbe demonstrates solid definition quality with clear naming, comprehensive descriptions, and proper schema definitions. Both tools follow verb_noun patterns (analyze_from_*) and include detailed parameter descriptions. Tool annotations are present (readOnlyHint, idempotentHint, openWorldHint). However, output schemas are not formally documented in the code, the description mentions JSON fields but no explicit schema definition is visible. Error handling is minimal; no recovery guidance for common failures (invalid base64, unsupported formats, password errors). Prompts are well-structured but add complexity without clear necessity.

• Add explicit return type schema to both tools. Define the structure of the JSON response with typed fields: {size: int, digest_sha256: string, format: string, entries: [{type: string, subject: string, issuer: string, not_before: string, not_after: string, fingerprint_sha256: string, key_algo: string, key_size: int, sig_algo: string, san: [string], usages: [string]}]}.
• Wrap tool logic in try-except blocks and return structured error responses. Example: if base64 decoding fails, return {error: 'Invalid base64', message: 'content_b64 must be RFC 4648 raw format without whitespace or newlines', suggestion: 'Verify the base64 string and retry'}.
• Document and enforce path validation in analyze_from_local_path. Show the resolve_path() implementation or add explicit validation: reject paths containing '..', symlinks, or files outside a configured allowlist. Add a description note: 'Path must resolve within the server's configured sandbox directory.'
• Remove or repurpose prompts. If audit_local_file and audit_base64_file are meant to provide domain expertise (e.g., flagging weak algorithms, expiry warnings), move that logic into the tools themselves as optional output fields. Otherwise, delete the prompts and let the LLM compose tool calls directly.
• Document result limits and truncation behavior. Add to tool descriptions: 'If a keystore contains more than 100 entries, only the first 100 are returned. Call with a specific entry index or name to retrieve additional details.' Implement pagination or filtering parameters if needed.