project_raster

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

No annotations provided, so description bears full burden. It mentions reading in_raster and writing out_raster within PathGuard allowed roots, and exposes resampling_type and cell_size. However, it omits details on overwrite behavior, error handling, or performance impacts, leaving gaps.

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: first defines purpose and method, second gives usage context, third lists key parameters and constraints. Efficient, well-structured, no redundancy.

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 the rich schema and presence of an output schema, the description covers essential usage and constraints. It misses mention of required out_wkid and overwrite behavior, but these are in the schema, so completeness is adequate.

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 input schema includes detailed descriptions for all parameters, so the description's mention of resampling_type and cell_size adds little new value. With high schema coverage, 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 the tool reprojects a raster dataset into another CRS, using ArcPy ProjectRaster. It provides specific use cases like aligning DEMs and imagery, which distinguishes it from vector projection or resampling tools among 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 description advises use before overlay, map algebra, extraction, or export, giving clear context. It implicitly excludes vector use but does not explicitly contrast with alternatives like resample_raster, which could refine guidance.

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