Map Spatial Reference

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds only a generic "returns verifiable structured results" claim and a vague "write and path restrictions depend on service capabilities" line, which is boilerplate rather than specific behavior for a read-only spatial-reference lookup.

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 the brevity comes from under-specification rather than economy; the two clauses are generic filler that do not earn their place.

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 detailed, but for a tool requiring an .aprx path and a map name the description should clarify what the spatial reference is and any preconditions. Given 0% parameter coverage and a nearly meaningless description, an agent cannot confidently invoke this.

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% and both required parameters (aprx_path, map_name) are undocumented anywhere. The description supplies no meaning, format, or example for either, so an agent has no basis beyond the parameter names.

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 the resource ("map地图") but never states the action: it does not say it retrieves/reads the map's spatial reference. The title and name carry the meaning; the description is close to a restatement and does not distinguish it from siblings like arcgis_pro_set_map_spatial_reference.

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?

No when-to-use guidance, no prerequisites, and no mention of the near-identical sibling arcgis_pro_set_map_spatial_reference (which mutates the same property). An agent gets nothing about selecting this over alternatives.

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