Select Layer By Location

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

Annotations declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the safety profile is already known. The description adds that the tool updates the selection set and verifies ArcPy-derived count consistency, but it does not explain what the verification does or any error conditions. With annotations covering the mutation profile, this is modest added value.

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?

A single front-loaded sentence with no wasted words. It is appropriately concise, though its brevity is part of the completeness problem rather than a structural flaw.

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?

For a complex 8-parameter spatial analysis tool with no schema descriptions, the description is far too thin. Annotations and the output schema help with safety and return values, but the description provides no parameter or usage context, leaving the agent to rely on the tool name alone.

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% for 8 parameters, and the description mentions no parameter names or values. It gives no guidance on overlap_type, selection_type, search_distance, or invert_spatial_relationship. It completely fails to compensate for the schema gap.

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?

States a specific verb (更新 selection set) and resource (图层选择集), and the spatial-relationship scope distinguishes it from the attribute-based sibling select_layer_by_attribute. However, it does not explicitly name any sibling alternative, so it stops short of 5.

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 when-to-use guidance, no conditions, and no alternatives are mentioned. The agent must infer from the tool name alone that this is the spatial counterpart to arcgis_pro_select_layer_by_attribute.

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