project_raster

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

With no annotations, the description should disclose behavioral traits. It mentions resampling methods but does not describe side effects (e.g., what happens if out_wkid is invalid, whether overwrite is safe, performance implications, metadata preservation). The description adds minimal value beyond the schema.

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 very concise (11 words) and front-loaded with the action. However, it includes redundant parentheses with '(ProjectRaster)', which is unnecessary. Still, efficient.

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 complexity of raster reprojection (spatial reference transformation, resampling, potential for errors), the description is too sparse. It does not explain output schema, coordinate system handling, or common pitfalls. A more complete description would prepare the agent for parameter interactions.

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 description does not explain individual parameters. Schema description coverage is 0%, so the description should compensate, but it only mentions resampling types, which are already in the schema enum. Parameters like 'in_raster', 'out_raster', 'out_wkid', 'cell_size', and 'overwrite' are left undocumented.

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 specifies the action ('Reproject a raster') and lists the resampling types. It distinguishes from siblings like 'resample_raster' (which changes cell size/resampling without projection change) and 'define_projection' (which assigns projection without transformation). However, 'reproject' could be more explicitly defined as changing coordinate system.

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 guidance on when to use this tool vs alternatives. There is no mention of prerequisites, typical use cases, or comparisons with similar tools like 'resample_raster' or 'clip_raster'. The description only states what it does, not when or why.

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