Gp Feature Class To Shapefile

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

Annotations already declare idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only a vague clause that write/path restrictions 'depend on service capabilities', which does not specify permissions, output location behavior, or overwrite semantics for a tool that writes a file to disk.

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?

It is short, but the brevity reflects under-specification rather than conciseness. The single sentence is generic boilerplate that conveys no actionable information and is not front-loaded with the actual operation.

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 two-parameter conversion tool with 0% schema coverage and no annotation coverage of parameters, the description is completely inadequate. The presence of an output schema excuses explaining return values, but nothing about inputs or behavior is provided.

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% for both parameters (input_features, output_folder), and the description adds no meaning about expected input format (feature class paths? layers?) or the output folder requirements. The description does nothing to compensate for the undocumented parameters.

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 reads 'ArcGIS Pro：feature要素' with no verb stating the operation. It never says the tool converts a feature class to a shapefile, so the agent must infer purpose from the name alone. This is tautological boilerplate rather than a stated 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 siblings like arcgis_pro_gp_export_features or arcgis_pro_gp_copy_feature_class. No prerequisites, exclusions, or alternatives are mentioned.

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