Gp Export Features

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

Annotations already indicate this is a non-read-only, non-destructive, idempotent, non-open-world operation. The description adds a vague note that write and path restrictions depend on service capabilities, but does not specify overwrite behavior, permissions, supported output formats, or error conditions.

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 description is short and front-loads the action. The second sentence is somewhat boilerplate and vague, but the overall structure is not bloated.

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 values need not be explained, and annotations cover the safety profile. Nevertheless, with 0% parameter description coverage and no when-to-use guidance, the definition is not complete enough for reliable invocation of this export tool.

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 compensate for two required parameters. It only implies a generic export from input features to an output path and provides no format, overwrite, path syntax, or validation semantics.

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 states a specific verb and resource ('导出要素' / export features), so the basic action is clear. However, it does not distinguish this tool from similar siblings such as arcgis_pro_gp_copy_features, arcgis_pro_gp_feature_class_to_shapefile, or arcgis_pro_gp_export_table, which prevents a 5.

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 like copy features, feature class to shapefile, or export table. The only caveat mentions service-dependent write/path limits, which is not actionable usage guidance.

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