Gp Intersect

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description's only added claim, "write and path restrictions per service capability," is vague boilerplate that does not specify permissions, overwrite behavior of out_feature_class, or path constraints concretely. It adds little beyond the structured hints.

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?

It is short, but the text is fragmented and machine-generated ("intersectgp intersect") rather than front-loading actionable information. Brevity here reflects under-specification, not efficiency.

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?

An output schema exists and the tool has two required parameters, but the description explains neither the operation, the parameters, nor the write semantics. For an overlay/geometry tool with no schema descriptions, this is inadequate.

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% and the description mentions neither in_feature_paths nor out_feature_class. Nothing compensates for the total lack of parameter documentation, including how multiple input paths relate or what happens if the output already exists.

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?

"intersectgp intersect" essentially restates the tool name/title without describing what the operation does. It never says it computes the geometric intersection of input features or writes overlapping portions to an output class, and does nothing to separate it from siblings like gp_union, gp_clip, gp_identity, or gp_symmetrical_difference.

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 guidance on when to use intersect versus the many overlapping overlay tools in the sibling list. No prerequisites, no exclusions, no alternative named.

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