arcgis_pro_environment_infoRead ArcGIS Pro geoprocessing environment settings and return structured, verifiable results to check write and path limits before running workflows.
ArcGIS Pro：读取环境地理处理环境。返回可验证的结构化结果；写入和路径限制以服务能力为准。
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| 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=true, idempotentHint=true, destructiveHint=false, so the safety profile is fully covered. The description adds only a generic claim ('returns verifiable structured results') plus a caveat that write/path limits depend on service capabilities — mildly useful but not concrete about permissions, scope, or failure modes.
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?
Two short sentences with the action front-loaded and no filler beyond the somewhat boilerplate second clause. Sized appropriately for a zero-argument info tool.
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 read-only nature. However, for an 'environment info' tool the description never enumerates what environments are reported, leaving the agent to infer scope from the output schema alone.
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?
The tool takes zero parameters, so per the baseline there is nothing for the description to disambiguate. No parameter semantics are needed and none are missing.
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+resource: reading the ArcGIS Pro geoprocessing environment settings. It is distinguishable from write-oriented siblings like arcgis_pro_validate_analysis_environment or arcgis_pro_set_project_defaults, though it never names an alternative or clarifies what 'environment' covers (workspace, extent, coordinate system, etc.).
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 guidance at all. With siblings such as arcgis_pro_validate_analysis_environment, arcgis_pro_project_summary and arcgis_pro_server_capabilities in the same family, the agent gets no signal about which one answers 'what are the current GP environment settings'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.