Gp Features To Json

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description does add one piece of non-structured context — that write and path restrictions depend on service capabilities — plus a claim of verifiable structured results, which goes modestly beyond the annotations.

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 brevity here comes from under-specification rather than discipline. The two sentences are fragmentary and much of the space is spent on a generic 'verifiable structured results' claim rather than on actionable content.

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, but a five-parameter writing tool with 0% parameter documentation and no usage guidance leaves the agent without enough to invoke it correctly or choose it over arcgis_pro_gp_json_to_features.

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% across all five parameters (in_features, out_json_file, format_json, include_m_values, include_z_values), so the schema itself gives almost no semantic help, and the description supplies none. Behaviors like the z/m value inclusion flags and JSON formatting are never explained anywhere.

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 reduces to 'ArcGIS Pro: features', which largely restates the tool name and title rather than stating a specific verb and resource. It never says the tool converts features to a JSON file, though the out_json_file parameter implies it, nor does it distinguish itself from the close sibling arcgis_pro_gp_json_to_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?

There is no statement of when to use this tool versus alternatives such as arcgis_pro_gp_json_to_features or arcgis_pro_gp_export_features. The only usage-adjacent note, 'write and path restrictions follow service capabilities', is a caveat rather than guidance.

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