The two tools serve clearly separate purposes: one returns the JSON Schema, the other validates a concrete posting. The descriptions explicitly contrast them (the schema deliberately omits duplicate-skill and intern/experience rules that only validation enforces), so an agent cannot mistake one for the other.

Both names follow a consistent snake_case verb_noun pattern (get_..._schema, validate_...), sharing the same 'job_posting' domain noun. The naming makes the read-vs-check relationship between the tools immediately legible.

Two tools is on the thin side, but the domain (schema retrieval + validation of a single document type) is narrow enough that each tool earns its place with no filler. A slightly richer surface (e.g. a template fetch) would round it out.

The core loop is closed: fetch the schema, then validate the whole posting and get field-level errors plus the parsed result when valid, including the multi-pass rule where hidden errors surface after fixes. The only minor gap is the absence of an example/template valid posting to bootstrap authoring.