Gp Idw

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 structurally. The description's only addition, '返回可验证的结构化结果；写入和路径限制以服务能力为准' (writes and path limits depend on service capability), is vague boilerplate that does not specify what is written, where, or under what constraints.

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 reflects under-specification rather than economy. The single substantive sentence is generic service boilerplate that is not front-loaded with anything an agent can act on.

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 five-parameter geoprocessing/interpolation tool with zero schema documentation, the description omits interpolation semantics, parameter meaning, and output behavior. An existing output schema covers return values, but nothing else the agent needs to invoke this tool correctly is present.

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 five parameters (power, z_field, cell_size, out_raster, in_point_features), and the description supplies no meaning for any of them. It does not explain that in_point_features is the source points, z_field the value to interpolate, or power the distance exponent, leaving the agent to guess entirely from terse names.

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 only echoes the tool's own name ('idwgp idw') without stating what IDW does (inverse distance weighted interpolation of point features to a raster) or how it differs from sibling interpolators such as arcgis_pro_gp_kriging. This is tautological restatement rather than a purpose 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?

No when-to-use, when-not-to-use, prerequisites, or alternative tool is mentioned. The agent gets no routing signal to distinguish this interpolation tool from kriging, kernel density, or point density siblings.

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