Gp Slope

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description's only addition, 'returns verifiable structured results; write and path restrictions depend on service capabilities', is generic boilerplate that does not disclose what actually happens to files, output rasters, or permissions.

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 content is redundant with the name and padded with boilerplate about 'service capabilities'. It is under-specified rather than tight, and mixes languages without adding clarity.

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 four-parameter raster GP tool with 0% schema coverage and no parameter detail in the description, the definition is not usable as a standalone guide. The existing output schema excuses it from explaining return values, but nothing compensates for the missing input semantics.

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 all four parameters (in_raster, out_raster, z_factor, output_measurement) are documented only by bare titles. The description contributes nothing about formats, measurement units, or defaults, leaving a critical semantic gap for output_measurement.

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 and title ('slopegp slope'), naming the tool family but never stating what a slope tool produces or how it differs from the many sibling raster tools such as arcgis_pro_gp_aspect or arcgis_pro_gp_hillshade. It is close to tautology rather than a specific verb+resource statement.

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 guidance, no prerequisites, and no mention of alternative tools. An agent gets no basis for choosing this over arcgis_pro_gp_aspect, arcgis_pro_gp_hillshade, or the generic arcgis_pro_gp_run_tool.

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