add_xy_coordinates

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

Discloses mutation (add/update fields) and recommends running on intended working dataset. No annotations provided, so description covers key behavioral traits, though could explicitly mention overwrite behavior.

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?

Three sentences front-load action, then use cases, then behavior. No fluff, 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 simple tool with one parameter and output schema, description covers purpose, use cases, and mutation. Prerequisites (point features) are clear. No gaps.

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 already has a detailed description for the single parameter (path with PathGuard). Tool description does not add new semantics beyond repeating schema info, meeting baseline.

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 adds or updates POINT_X and POINT_Y fields on point features using ArcPy AddXY, distinguishing it from generic field tools.

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?

Explicitly lists use cases (export, QA/QC, labeling, tabular analysis, integration) and warns about mutation, guiding when to use and caution.

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