Gp Calculate Geometry

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds valuable behavioral context by naming the required destructive gate, target/field mapping echo, and record count confirmation, which go beyond the annotations. It does not detail what happens to existing field values, but it meaningfully complements 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 single Chinese sentence is front-loaded with the core purpose and then lists safety requirements with no wasted words. It is dense but appropriately sized for a one-line summary, though it could be slightly more structured.

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 7-parameter destructive mutation tool with 0% schema description coverage and no visible output schema details needed, the description leaves critical gaps. It does not explain key parameters like area_unit, length_unit, or the geometry_property format, nor does it distinguish the tool from similar siblings.

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%, so the description must carry full parameter semantics. It maps to the confirmation parameters (target/field mapping echo, record count confirmation), but it omits meaning for area_unit, length_unit, and the nested array structure of geometry_property. Compensation is only partial.

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?

States a specific verb (计算) and resource (几何属性) with scope (现有字段整表), which is clear. It does not explicitly differentiate from the closely related sibling arcgis_pro_gp_calculate_field, but the focus on geometry and whole-table computation gives enough distinction.

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?

The description implies usage conditions by requiring destructive gate, target/field mapping echo, and record count confirmation, but it never states when to use this tool versus alternatives like arcgis_pro_gp_calculate_field. Guidance is present but incomplete.

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