geometry_op

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

With no annotations, the description carries the full behavioral burden, but it does disclose useful context: it uses Esri's public Geometry service and requires no key. It does not mention remote-call implications, rate limits, error behavior, or whether the input geometry is left unchanged, leaving meaningful gaps for an unannotated tool.

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 short, front-loaded, and wastes no words. The operation breakdown is compact and directly tied to invocation choices.

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 output schema exists, so return values need not be described. Still, for a 7-parameter, unannotated tool with 0% schema description coverage, the description is only partially complete: it covers the main operation-to-parameter relationships but omits unit vocabularies, validation expectations, and service limitations.

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%, so the description must compensate. It usefully maps operation modes to parameters: project uses in_sr/out_sr, buffer uses distance with unit, and simplify uses max_deviation in input SR units. It still leaves unit allowed values, SR ID expectations, geojson format details, and optional-parameter behavior unexplained.

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 names three specific operations (project, buffer, simplify) on a clearly scoped resource: one GeoJSON geometry. It also identifies the backing service, Esri's public Geometry service, so an agent can distinguish this computational geometry tool from the data, map, geocode, and export siblings.

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 operation-specific notes imply when each mode is appropriate: project for SR conversion, buffer for distance expansion, simplify for deviation reduction. However, there is no explicit when-to-use or when-not-to-use guidance and no comparison against siblings such as build_map or arcgis_request.

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