Gp Clip Raster

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is largely covered. The description adds mild behavioral context ('returns verifiable structured results; write and path restrictions subject to service capabilities'), which hints that output paths may be limited, but it stays vague about what gets written or where.

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?

Two short clauses, front-loaded with the action. It is efficiently sized, though the second clause about write/path restrictions is boilerplate rather than task-specific information.

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?

This is a write-producing geoprocessing tool with 6 parameters at 0% schema coverage. Although an output schema exists and annotations cover the safety profile, the description provides no parameter guidance and no usage context, so it is not complete enough for an agent to invoke it correctly without guessing.

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 description coverage is 0% across 6 parameters, so the schema gives the agent no parameter semantics and the description must compensate. It does not mention in_raster, out_raster, rectangle, clipping_geometry, in_template_dataset, or environment at all, leaving every parameter 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 states a specific verb and resource ('ArcGIS Pro: Clip raster'), so an agent knows this clips raster data. However, it does not differentiate from close siblings such as arcgis_pro_gp_clip (feature clipping) or arcgis_pro_gp_clip_raster_checked, leaving the agent to infer which variant to pick from the name alone.

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?

There is no when-to-use guidance, no prerequisites (e.g., what geometry defines the clip), and no mention of alternatives like the 'checked' variant. The agent is given no routing information beyond the tool name.

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