Gp Hillshade

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

Annotations already state readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false. The description adds only vague boilerplate ('returns verifiable structured results; write and path restrictions depend on service capabilities') that does not concretely describe what gets written, overwrite behavior, or path constraints. It does not contradict the annotations, but adds little beyond them.

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?

Brief, but the opening is redundant and garbled ('ArcGIS Pro：hillshadegp hillshade'), and the trailing sentence is generic filler. It is short without being informative.

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 raster-producing geoprocessing tool with five undocumented parameters and no annotation depth, the description is far too thin to let an agent invoke it correctly.

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% and the description provides no information about any of the five parameters (in_raster, out_raster, azimuth, altitude, z_factor). Nothing compensates for the undocumented schema, leaving the agent to infer meaning from parameter titles alone.

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 'hillshade' but supplies no verb or explanation of the operation – it does not say it computes hillshade shading from an input raster. 'hillshadegp hillshade' is effectively a restatement of the tool name/title, offering no differentiation from siblings like arcgis_pro_gp_slope or arcgis_pro_gp_aspect.

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 guidance on when to use this tool versus alternatives such as arcgis_pro_gp_slope, arcgis_pro_gp_aspect, or the generic arcgis_pro_gp_run_tool. No prerequisites, no exclusions, no context of any kind.

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