merge_features

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

Without annotations, the description describes that it reads input feature paths and writes a new output inside PathGuard roots, but lacks details on error handling, schema compatibility requirements, or performance. It provides basic behavioral context but is not exhaustive.

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 three sentences, front-loaded with purpose, and contains no redundant information. Every sentence adds value.

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?

Given the output schema exists, the description covers the core functionality but omits details on compatibility conditions, error scenarios, or side effects. It is complete for a basic understanding but lacks depth.

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?

With 0% schema description coverage, the description must compensate for parameter meaning, but it only mentions 'reads input paths and writes output' without elaborating on parameters like overwrite, in_features, or out_features. The schema itself has descriptions, but the tool's description does not add value beyond that.

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 combines multiple compatible feature classes or layers into one output using ArcPy Merge. It specifies the use case of assembling same-schema datasets from multiple sources, tiles, districts, or batches, distinguishing it from siblings like append_features or copy_features.

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 provides clear context on when to use the tool ('assemble same-schema datasets from multiple sources'), but does not mention when not to use it or explicitly name alternative tools, though the context implies it is for merging compatible inputs.

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