Calculate Las Statistics

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

Description correctly discloses a destructive-gate workflow with target echo and fixed confirmation phrase for forced recompute — going beyond annotations. However, it conflicts in spirit with destructiveHint=false and idempotentHint=true annotations, since '强制重算' (forced recompute) and an overwrite confirmation imply mutation of existing stats; the annotations reduce the safety disclosure burden but the description's gating language doesn't fully explain the mismatch.

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?

A single compact sentence with no filler, but it front-loads the destructive-gate mechanics while omitting more basic operational context, so information density is uneven.

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 8-parameter mutation-adjacent tool with 0% schema coverage and no output schema mentioned in the description; the description covers only the overwrite-gate path and neglects the default SKIP_EXISTING_STATS flow and report output 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 the description names only las_dataset, expected_las_dataset (target echo), and the confirmation phrase concept. It does not explain summary_level, calculation_type, delimiter, decimal_separator, or out_report — six undocumented parameters left to the agent to infer.

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?

Clear specific verb (calculate) plus resource (LAS statistics) and mentions report export, distinguishing it from sibling arcgis_pro_las_dataset_info and arcgis_pro_build_las_pyramid. The destructive-gate phrasing is unusual but purpose remains identifiable.

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 guidance on when to use this versus arcgis_pro_las_dataset_info or arcgis_pro_build_las_pyramid, and no explanation of the calculation_type enum values (e.g., SKIP_EXISTING_STATS) that clearly gate behavior. The '强制重算' (forced recompute) phrasing hints at a mode but doesn't state when to choose it.

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