Gp Table Select

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=false. The description adds a generic note that results are structured and that write/path restrictions depend on service capabilities, which gives some behavioral context beyond the annotations. It does not specify what gets written or overwritten, nor any auth or rate-limit details.

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-loads the tool name and action, but the second sentence is boilerplate that adds little actionable value. It is not bloated, but it is under-specified rather than optimally concise.

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. However, for a tool with three completely undocumented parameters and mutation-capable annotations, the description omits essential context such as output table behavior, WHERE clause semantics, and write constraints.

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 all three parameters (in_table, out_table, where_clause). The description provides no explanation of any parameter, so it does not compensate for the schema's lack of field descriptions.

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 says only 'ArcGIS Pro: Select table' (选择表), which essentially restates the tool name and title. It does not state that this GP tool selects rows from an input table into a new output table using a WHERE clause, nor does it distinguish it from sibling selection tools such as arcgis_pro_select_table_by_attribute or arcgis_pro_gp_analysis_select.

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, when-not-to-use, or alternative-routing guidance is provided. The sentence about write and path restrictions is a generic caveat, not a usage condition that would help an agent choose this tool over any sibling.

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