check_mapping

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden, and it does disclose the checks performed (schema conformance plus binding to the model's current schema). However it says nothing about whether validation is read-only, whether it mutates the mapping file, what the result looks like on failure, or that ct_id triggers a network/package fetch from the host.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with no filler; the two capabilities are ordered sensibly. Slightly overstuffed comma structure costs a point but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema and no annotations, so the description should say more about what a validation result or failure mode looks like and about the fetch implied by ct_id. It covers both operating modes but leaves the agent guessing about the return contract.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents mapping, ct_id and directory including the 'give this or ct_id, not both' constraint. The description only gestures at the model-vs-file distinction ('given a model'), adding little beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Names two specific verbs (validate, check binding) on a well-defined resource (mapping file against mapping schema / model schema) – the agent can tell this apart from siblings like map_record and fidelity, which transform or score rather than validate. It stops short of explicitly contrasting with those siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the situation ('given a model, check it is bound to that model's current schema') but never states when to use this versus map_record or fidelity, nor any prerequisites. Usage is inferable from the phrasing rather than spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.