import_from_geojson

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

With no annotations, the description discloses constraints (PathGuard allowed roots) and behavior (overwrite required for existing outputs), but does not detail error handling or performance characteristics.

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?

Two sentences, no extraneous words, front-loaded with purpose. 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 tool has multiple parameters and an output schema (per context), the description covers input, output, and constraints adequately, but could elaborate on return values or error cases.

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 coverage is 0%, so description is the sole source. It adds context for 'in_json' and 'out_features' (PathGuard, overwrite), but the 'overwrite' parameter is only mentioned in passing, and not all parameters are described in detail.

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 converts GeoJSON to an ArcGIS feature class using ArcPy JSONToFeatures, specifies the verb 'convert' and the resource, and distinguishes from sibling tools like export_to_geojson.

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 for when to use the tool ('bring web, API, or exchange-format vector data into a geodatabase'), but does not explicitly state when not to use it or mention alternatives.

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