Assign Domain To Field

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

Annotations already disclose this is a non-read-only, idempotent, non-destructive, non-open-world mutation, and the description does not contradict them. However, it adds nothing beyond the annotations: it does not say what gets altered (the dataset schema), whether the change overwrites an existing domain assignment, or what permissions/preconditions apply.

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?

A single front-loaded sentence with no wasted words, which is good. But for a 4-parameter schema-mutating tool it is arguably under-specified rather than genuinely concise, so it lands at the minimum-viable level.

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?

An output schema exists so return values need not be explained, but this is a mutation tool with zero schema description coverage and only annotation-level behavioral disclosure. It omits preconditions, the effect on existing assignments, and parameter meaning, leaving real gaps 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 description coverage is 0%, so the description carries the burden but only hints at the optional subtype_code constraint. dataset_path, field_name, and domain_name are self-evident from their names, but subtype_code's meaning (a subtype code value used to scope the assignment) is barely conveyed.

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+resource ('assign domain to field') and notes the subtype-code scoping, so an agent can tell this is a schema-editing operation distinct from read-only domain listing. It does not, however, differentiate itself from the sibling arcgis_pro_remove_domain_from_field or the other domain tools, so a 4 rather than 5.

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?

There is no when-to-use guidance, no prerequisite (e.g. that the domain must already exist via arcgis_pro_create_domain), and no mention of alternatives such as arcgis_pro_remove_domain_from_field. The only conditional hint is that subtype_code may optionally narrow the assignment.

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