Gp Reclassify

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, so the mutation profile is covered structurally. The description adds only a vague disclaimer that write/path restrictions follow service capability, which is marginally useful but not operation-specific (no mention of overwrite behavior on out_raster or the remap/remap_mode semantics).

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?

It is short, but the brevity comes from duplication ('reclassifygp reclassify') rather than efficiency, and the generic boilerplate about 'verifiable structured results' consumes the remaining space without conveying anything actionable.

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 geoprocessing tool with 0% schema coverage, the description is far too thin. The output schema exists, so return values need not be explained, but nothing compensates for the missing parameter and usage context.

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 (in_raster, reclass_field, remap, out_raster, remap_mode, missing_values), yet the description supplies no parameter meaning, format, or defaults. Remap string syntax and remap_mode values are entirely undocumented 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 essentially restates the tool name twice ('reclassifygp reclassify') with no specific verb+resource framing that an agent could use to distinguish this from siblings like arcgis_pro_gp_raster_calculator, arcgis_pro_gp_resample, or arcgis_pro_gp_raster_con. It never says it reclassifies raster values via a remap table, which is the actual operation.

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, prerequisite, or alternative-tool guidance. Nothing tells the agent when reclassification is the right choice versus other raster tools in the sibling list.

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