Build Mosaic Overviews

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

Annotations already declare idempotentHint=true, destructiveHint=false, and readOnlyHint=false, so the safety profile is covered. The description adds that only missing or stale overviews are touched, which is useful behavioral context, but it omits what 'controlled targets' means and any prerequisite or cost information.

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 filler, and the core operation leads. It is efficient, though the brevity tips toward under-specification given the 7-parameter surface.

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 for a 7-parameter mutation with 0% schema coverage and no usage guidance, the description leaves major gaps. An agent cannot determine parameter intent or safe invocation from this text alone.

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 7 parameters, so the description must compensate and largely fails. The mention of 'missing or stale' loosely maps to generate_missing_images and regenerate_stale_images, but define_missing_tiles, generate_overviews, where_clause, and environment receive no explanation anywhere.

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 specific verb pair (define and generate) and resource (mosaic dataset overviews) plus the scope constraint (missing or stale). An agent can grasp the operation, but it never distinguishes itself from siblings like arcgis_pro_build_mosaic_footprints or arcgis_pro_raster_build_pyramids.

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 alternative guidance. 'Limited to controlled targets' hints at scoping but never explains what a controlled target is or when this should be chosen over other mosaic maintenance tools.

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