List Fields

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description's second clause ('write and path restrictions depend on service capabilities') is boilerplate that adds no concrete behavior for a pure read tool, and says nothing about output shape, ordering, or error cases.

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?

Very short and front-loaded, which is good, but the second clause is filler that neither informs invocation nor clarifies the resource being listed.

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 only required input is undocumented and the target resource is ambiguous among many list_* siblings. The definition is not complete enough for reliable selection and invocation.

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 the single required parameter dataset_path, so the description must compensate and it does not — no mention of accepted path forms (GDB, feature class, table, SDE connection). The path concept is only implied by '路径限制'.

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 the verb+resource (list fields) for ArcGIS Pro, but is generic: it never says the fields belong to a dataset identified by dataset_path, and it does not distinguish itself from close siblings such as arcgis_pro_list_field_groups, arcgis_pro_list_subtypes, or arcgis_pro_dataset_schema.

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?

Provides no when-to-use, prerequisites, or alternative routing. Nothing tells the agent whether to call this instead of dataset_schema or list_field_groups for a given intent.

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