copy_features

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

With no annotations, the description carries the full burden. It states the tool reads in_features and writes out_features, mentions PathGuard constraints, and the overwrite flag. It implies non-destructive behavior ('safe working copy') but does not detail what happens if input is a layer vs feature class or any size limits.

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 two sentences: first sentence gives purpose and method, second adds PathGuard and overwrite context. No unnecessary words, well front-loaded.

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?

The description covers the essential context: input/output paths, PathGuard constraints, and overwrite behavior. It does not mention return values, but an output schema exists (not shown). It could mention that all features are copied, but overall it's sufficiently complete for use.

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 input schema already describes parameters (in_features, out_features, overwrite) with clear descriptions. The tool description adds no additional semantic value beyond what the schema provides, so a baseline score of 3 is appropriate.

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 clearly states the tool copies a feature class or layer using ArcPy CopyFeatures, preserving geometry, attributes, schema, and spatial reference. This distinguishes it from siblings like create_feature_class (empty creation) or export_to_shapefile (format conversion).

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 advises using it to create a 'safe working copy' and mentions PathGuard allowed roots and overwrite requirement. However, it does not explicitly state when not to use it or suggest alternatives like export_to_shapefile for format conversion.

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