Raster Build Pyramids

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

The description adds real behavioral context the annotations lack: a delete mode exists and is gated by an explicit destructive confirmation plus exact source-path echo. But this conflicts with the declared destructiveHint=false, and the description does not reconcile the two or explain whether the default build path is idempotent, how long the operation takes, or whether it locks the dataset.

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?

Very compact and front-loaded: the primary build/update action comes first, with the destructive-delete caveat second. Every clause carries meaning, though the phrasing is terse enough that it reads as a fragment rather than a full explanation.

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 described. But for a 9-parameter raster-mutation tool with 0% schema documentation and no parameter docs in the description, the definition is far short of what an agent needs to invoke it correctly. There is no coverage of compression, resampling, pyramid levels or the environment argument.

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 9 parameters, so the schema alone gives an agent almost nothing. The description only hints at confirm_delete_pyramids (via '源路径精确回显') and says nothing about pyramid_level, skip_existing, compression_type, resample_technique or skip_first, leaving most parameters semantically opaque.

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+resource ('构建或更新栅格金字塔' — build or update raster pyramids), which clearly identifies the operation. It does not distinguish itself from sibling raster tools such as arcgis_pro_build_las_pyramid, arcgis_pro_build_mosaic_overviews or arcgis_pro_raster_calculate_statistics, so an agent must infer which pyramid-building tool applies.

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 second clause implies a usage condition — deletion is a separate mode that requires a destructive gate and exact source-path echo — which gives some idea of when the destructive path applies. However, there is no guidance on when to use this tool versus the other raster/maintenance siblings, nor on prerequisites like the raster needing statistics or being a valid format.

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