Repair Layer Source

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is largely covered. The description adds only a vague note that 'write and path restrictions are subject to service capabilities,' which hints at path/write constraints but names no concrete limitation, and 'returns verifiable structured results' is redundant given the output schema exists.

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 purpose is front-loaded and the text is short, but the second clause is generic boilerplate ('verifiable structured results,' 'subject to service capabilities') that occupies most of the description without adding actionable information. Brevity here reflects under-specification rather than efficient writing.

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?

For a 6-parameter mutation tool with zero schema descriptions and several write/path-sensitive inputs, the description is far too thin. Although an output schema exists and need not be restated, nothing explains which layer gets repaired, what happens to the existing source, or how the new workspace/dataset arguments interact.

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% across 6 parameters, including the non-obvious ones (workspace_type, new_dataset_name with an empty-string default), so the description carries the full burden of explaining them. It mentions nothing about aprx_path, map_name, layer_name, new_workspace_path, or the defaults, leaving every parameter undocumented.

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 names a verb and resource ('Repair Layer'), so the general action is identifiable, but it never says what repairing means concretely (repointing a layer's data source to a new workspace). It offers no differentiation from nearby siblings such as arcgis_pro_layer_replace_data_source, arcgis_pro_list_broken_sources, or arcgis_pro_connection_repair_apply.

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, when-not-to-use, or prerequisite information. An agent cannot tell from this text whether to repair a source here, use layer_replace_data_source, or run the connection_repair_preflight/apply pair first.

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