arcgis_pro_open_layer_table_viewOpen and activate a layer's attribute table in the current ArcGIS Pro session, optionally showing only selected records.
在 CURRENT ArcGIS Pro 中打开并激活图层属性表，可仅显示当前选择记录。
| Name | Required | Description | Default |
|---|---|---|---|
| aprx_path | Yes | ||
| layer_name | Yes | ||
| show_selected | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=false, covering the safety profile. The description adds that the view is activated and can be limited to the current selection, but does not disclose project-context requirements or side effects beyond activation.
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?
A single short sentence, front-loaded with the action and resource. 'CURRENT' clarifies execution context without padding, and every element earns its place.
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 described, and annotations cover the safety profile. However, with 0% schema description coverage, the required aprx_path is unexplained and no usage alternatives are given, making the definition adequate but incomplete.
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 must carry parameter meaning. It indirectly addresses layer_name ('图层属性表') and show_selected ('当前选择记录'), but the required aprx_path parameter is not explained at all, leaving a significant gap.
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 a specific verb and resource ('打开并激活图层属性表') and scopes it to CURRENT ArcGIS Pro. It does not distinguish from sibling view/table openers such as arcgis_pro_sdk_open_table or arcgis_pro_make_table_view, so it is clear but not fully differentiated.
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/when-not guidance or alternative-tool routing is provided. The phrase '可仅显示当前选择记录' describes a capability of show_selected, not when to select this tool over siblings like arcgis_pro_sdk_open_table or arcgis_pro_open_report_view.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.