get_spatial_reference

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

With no annotations provided, the description fully discloses that the tool is a pure lookup, has no filesystem input/output, and does not modify datasets. It also indicates the kind of information returned (CRS name, type, datum, units), which compensates for the lack of 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?

The description is two sentences with no redundant words, front-loading the action and adding necessary context efficiently.

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?

For a simple lookup tool with one parameter and an output schema, the description fully covers the purpose, usage, and behavioral constraints, making it complete without exceeding needs.

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?

The schema description coverage is 0% per context signals, but the description does reinforce the parameter's purpose (WKID/EPSG) and usage context. However, it does not add new information beyond what the schema's parameter description already provides, so a baseline 3 is appropriate.

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 it looks up an ArcGIS spatial reference by WKID or EPSG code using arcpy.SpatialReference, which is a specific verb and resource. Among sibling tools, this is distinct from projection or modification tools like define_projection or project_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 explicitly advises using it before projection workflows to verify CRS attributes, and clarifies it is a pure lookup with no filesystem I/O or dataset modification, providing clear when-to-use and when-not-to-use guidance.

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