arcgis_pro_gp_dissolveAggregates input features by a dissolve field and writes a new feature class, simplifying boundary and attribute data for spatial analysis or mapping.
ArcGIS Pro：dissolvegp dissolve。返回可验证的结构化结果；写入和路径限制以服务能力为准。
| Name | Required | Description | Default |
|---|---|---|---|
| in_features | Yes | ||
| dissolve_field | No | ||
| out_feature_class | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description vaguely mentions 'write and path restrictions subject to service capabilities' but does not clarify whether input data is modified, what output is created, or any other behavioral trait beyond the annotations.
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 poorly structured, consisting of a malformed fragment followed by generic boilerplate. It is under-specified rather than genuinely concise, and neither sentence conveys useful information for invoking the tool.
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?
Given a geoprocessing tool with three undocumented parameters, no schema descriptions, and an output schema that the description does not reference, the definition is completely inadequate. It omits essential details about inputs, outputs, and prerequisites.
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?
The tool has three parameters (in_features, dissolve_field, out_feature_class) with 0% schema description coverage. The description provides no meaning for any parameter, so it fails to compensate for the missing schema documentation.
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 restates the tool name ('dissolvegp dissolve') and adds generic boilerplate ('returns verifiable structured results'), but never explains what the dissolve operation actually does, such as aggregating features based on attribute values. This is a tautology rather than a clear statement of purpose.
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. The sibling list includes many other geoprocessing tools (e.g., arcgis_pro_gp_aggregate_polygons, arcgis_pro_gp_merge), yet the description mentions no context, prerequisites, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.