Gp Analysis Select

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

Annotations disclose readOnlyHint=false, idempotentHint=true, and destructiveHint=false, but the description only vaguely mentions write/path restrictions without explaining what the tool actually writes, whether it overwrites existing outputs, or any rate limits. The note '返回可验证的结构化结果' is a generic statement that adds little.

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 short and front-loaded, but it wastes the opportunity to provide value; brevity here stems from under-specification rather than efficient communication. Still, it contains no extraneous detail, so a mid-range score is warranted.

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, so return values need not be explained, but the tool's core operation, parameter meaning, and usage context are entirely missing. This is a complex GP tool with required inputs and an optional clause; the description fails to provide any operational context.

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%, so the description bears full responsibility for explaining parameters, yet it provides no information on 'in_features', 'where_clause', or 'out_feature_class'. The mention of '路径限制' hints at output paths but is too vague to be useful.

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 is largely a tautology, restating the tool name 'gp analysis select' without clarifying what the operation does (e.g., select features by attribute and write to a new feature class). The Chinese phrasing '选择gp analysis select' is effectively a restatement of the name, offering no specific verb+resource description that distinguishes it from siblings.

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 or when-to-avoid guidance is provided. The vague phrase '写入和路径限制以服务能力为准' about write/path limits does not indicate which scenarios the tool is appropriate for or which alternatives (e.g., arcgis_pro_gp_table_select, arcgis_pro_select_layer_by_attribute) should be used.

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