Create Mosaic Dataset

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

Annotations already declare the write/non-destructive/non-idempotent profile, so the bar is lower, but the description only adds that the workspace is new and the output is verified. For a mutating 8-parameter GP tool with no schema descriptions, it omits any note on permissions, coordinate-system requirements, or what verification entails.

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 compact sentence with the resource front-loaded and no filler. It is efficient, though brevity here is partly achieved by omitting necessary detail rather than by tight 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?

This is the most complex tool class in the sibling set (8 params, GP environment, additionalProperties object), yet the description gives no parameter meaning, no prerequisites, and no follow-up workflow. An output schema exists, so return values need not be explained, but the invocation side is severely under-covered.

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 8 parameters, including required in_workspace, in_mosaicdataset_name, and coordinate_system. The description mentions none of these by name and adds no format, units, or accepted-value guidance, leaving the schema fully 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?

States a specific verb (create) and resource (mosaic dataset), scoped to a new geodatabase workspace in the GP output root. It is distinguishable from siblings like arcgis_pro_add_rasters_to_mosaic_dataset or arcgis_pro_create_feature_dataset, though it never names those alternatives explicitly.

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?

No when-to-use guidance, no prerequisites, and no routing to related tools such as build_mosaic_footprints or add_rasters_to_mosaic_dataset, which are the natural next steps. The agent must infer usage entirely from the name.

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