Gp Project Raster

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is covered structurally. The description's 'returns verifiable structured results; write and path restrictions follow service capability' is generic boilerplate that adds no tool-specific behavior — it does not explain that an output raster is written to disk, whether it overwrites an existing out_raster, or what capability limits mean in practice.

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?

The text is short, but brevity here is under-specification rather than conciseness: two clauses of generic boilerplate that carry no actionable content for a four-parameter geoprocessing tool. Nothing meaningful is front-loaded because there is nothing meaningful to front-load.

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-value explanation is not required, but the description supplies nothing else for a tool that writes a new raster and requires a target WKID. Given 0% schema coverage and no param documentation, the description is wholly inadequate for correct invocation.

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 four parameters, and the description mentions none of them. in_raster, out_raster, out_wkid (a spatial reference WKID) and resampling_type (NEAREST default) are all left entirely undefined, including the crucial meaning of out_wkid — the single most important value the agent must choose correctly.

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 ('ArcGIS Pro: project工程') without saying what is projected onto what. It never states that this reprojects a raster to a new spatial reference defined by out_wkid, and it does not differentiate from the very close siblings arcgis_pro_gp_project, arcgis_pro_gp_resample, or arcgis_pro_gp_clip_raster.

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 statement of when to use this tool versus alternatives such as arcgis_pro_gp_project (vector projection) or arcgis_pro_gp_resample. No prerequisites, no input-type constraints, no exclusions — nothing an agent could use for routing.

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