Two tools with complete input schemas and descriptions. add_company has clear, concise description (79 chars) and well-typed parameters with enums for size/remote_policy. add_job_posting is more complex with 16 parameters, comprehensive descriptions, and proper enum constraints (source, priority). Both tools lack output schema documentation, responses are inferred from code (JSON success objects). Error handling returns isError flag with text messages but lacks recovery guidance. No tool annotations (readOnlyHint/destructiveHint/idempotentHint). Naming follows verb_noun pattern correctly. Parameter descriptions are generally good (50-150 chars each) but some lack format/constraint details (e.g., posted_date/closing_date mention YYYY-MM-DD but no validation shown).

• Add explicit output schema documentation for both tools. Example: 'Returns {success: boolean, message: string, company: {id, name, industry, ...}}' or similar structured format.
• Add tool annotations: destructiveHint=true for both tools (they write to database); idempotentHint=true for add_job_posting (upsert on URL is idempotent).
• Enhance error messages with recovery guidance. E.g., 'Company lookup failed: {error}. Try create_company first if the company does not exist.' or 'Invalid URL format. Ensure URL starts with http:// or https://'.
• Add regex pattern or format constraint to date parameters. Use z.string().regex(/^\d{4}-\d{2}-\d{2}$/) in Zod schema and document in description.
• Document parameter dependencies in add_job_posting. E.g., 'created_by_reason is optional but recommended to explain why this posting was created (e.g., for audit trails).'