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

The description goes well beyond annotations, disclosing conflict resolution ('imported rule wins on a pattern conflict'), target translation by display name, the 'one model = one set' model, the need to re-sync to classify, and the read-only API key restriction. It does not contradict the annotations (readOnlyHint false, destructiveHint false).

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?

The description is dense but each sentence serves a purpose: core action, conflict behavior, template_id sourcing, re-sync instruction, and API key restriction. It is front-loaded with the main action and avoids fluff, though slightly longer than necessary.

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?

Despite having no output schema, the description covers the mutation's effects, conflict resolution, follow-up re-sync, and access restrictions. It also references the source of template_id. The summary and model_id parameters are already well documented in the schema, so the description is complete enough for correct invocation.

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 coverage is 100%, so the baseline is 3. The description adds meaning to template_id by specifying it comes from layerz_list_mappings and can be a system_template or user_template, and also mentions 'or one of your catalogs'. It reinforces the 'one model = one set' constraint, providing extra context 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?

The description states a specific verb and resource ('Import a mapping template ... by DUPLICATING its rules into the model's single mapping set'), and explicitly clarifies that this is how a template 'applies' with no implicit cross-model application. This distinguishes it from sibling tools like layerz_promote_template and layerz_set_mapping.

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 explains when to use it (to apply a template/catalog to a model), gives the source for template_id (layerz_list_mappings templates), and notes it is unavailable for read-only API keys. It does not explicitly name alternative tools to use instead, but the context strongly implies it is the only way to apply a template.

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