Gp Frequency

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description's only added claim — that write and path restrictions depend on service capability — is too vague to tell an agent what will be written, where outputs land, or whether existing tables are overwritten.

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 length is spent on generic filler ("返回可验证的结构化结果") rather than front-loading useful 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, so return values need not be explained, but a 4-parameter geoprocessing tool with 0% schema coverage needs the description to carry parameter and behavior context and it does not. An agent cannot determine input/output table semantics or field-list format from this text.

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 4 parameters (3 required), and the description names none of them. With no schema-level descriptions, the description had the full burden of explaining in_table, out_table, frequency_fields, and summary_fields and provides nothing.

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 essentially restates the tool name ("frequencygp frequency") without stating a verb+resource in a meaningful way. It never says it computes frequency counts of attribute values in a table, which is what the sibling-named parameters (in_table, out_table, frequency_fields) imply. It is a tautology padded with generic boilerplate.

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 indication of when to use this tool versus siblings such as arcgis_pro_gp_statistics, arcgis_pro_da_distinct_values, or arcgis_pro_gp_table_select. The clause "写入和路径限制以服务能力为准" (write/path limits depend on service capability) is not actionable guidance.

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