resample_raster

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It mentions reading one input and writing an output, but does not cover important behaviors like overwrite semantics, error conditions, performance implications, or whether the operation is reversible. This is insufficient for a tool with no annotation support.

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 concise: two sentences that cover purpose, usage, and output. It is front-loaded with the core action and provides essential context without unnecessary details.

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?

The description adequately explains the input/output relationship and usage context. Since the tool has an output schema, the description does not need to detail return values. It covers the essential aspects for an agent to understand when and how to invoke the tool.

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?

Despite the context signal indicating 0% schema coverage, the input schema actually includes descriptions for all parameters. The description adds minor value by advising on resampling method choice for categorical vs continuous data, but mostly repeats what is already in the schema. 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's purpose: 'Change raster cell size using ArcPy Resample.' It also mentions use cases like alignment before overlay, modeling, etc. While it doesn't explicitly distinguish from siblings, the action is specific enough to stand apart from other raster 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?

The description provides guidance on when to use the tool ('align resolution before overlay, modeling, visualization, or export') and mentions choosing resampling methods based on data type. However, it lacks explicit when-not-to-use instructions or comparisons with alternatives like project_raster.

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