List Layout Elements

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description's only added claim — "write and path restrictions depend on service capability" — is generic and largely irrelevant to a read-only listing tool, so it contributes little beyond the annotations.

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 and front-loaded, which is good, but the second sentence is template boilerplate that does not earn its place for a read-only listing tool. Length is fine; content density is low.

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, with two required parameters and an optional filter all undocumented, and no indication that this lists elements of a specific layout (as opposed to layouts themselves), the definition is not complete enough for an agent to invoke it correctly.

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 three parameters (aprx_path, layout_name, element_type), and the description adds no information about any of them — no format for the .aprx path, no statement of whether layout_name is exact-match, and no explanation of what element_type values are accepted (it has no enum and a blank default). With zero coverage and zero compensation, the description leaves the required inputs undocumented.

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 "列出布局" (list layouts), which directly duplicates the sibling arcgis_pro_list_layouts and does not match the tool's own name arcgis_pro_list_layout_elements — nothing is said about listing the elements contained within a layout. An agent could easily route to the wrong sibling. It restates a generic verb+ArcGIS Pro context without identifying the actual resource.

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 when-to-use guidance, no prerequisite (e.g., that an aprx and a layout name are needed), and no mention of alternatives such as list_layouts or list_layout_map_frames. The clause about "service capability" boundaries is boilerplate rather than routing guidance.

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