Mapframe Extent

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 by structured data. The description's generic boilerplate ('returns verifiable structured results; write and path restrictions are subject to service capabilities') adds no tool-specific behavior such as whether it reads the current extent or the frame's reference extent, or what happens if the mapframe name is not found.

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 brevity reflects under-specification rather than efficiency — one clause repeats the title and the other is generic service boilerplate. Nothing about the tool's actual behavior is front-loaded.

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, but for a read tool with three undocumented required parameters and a confusingly similar sibling, the definition leaves an agent without enough to invoke it correctly or distinguish it from set_mapframe_extent.

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?

All three required parameters (aprx_path, layout_name, mapframe_name) have 0% schema description coverage, and the description supplies no meaning, format, or path expectations for any of them. With the schema providing no help, the description fully fails to compensate.

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 ('ArcGIS Pro：mapframe地图框') merely restates the title 'Mapframe Extent' in Chinese and never states a verb — get, read, or return the extent. Nothing distinguishes it from the sibling arcgis_pro_set_mapframe_extent, which the name alone implies but the text does not clarify.

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. project/layout must be open), and no mention of the near-identical sibling arcgis_pro_set_mapframe_extent. An agent has no textual basis for choosing this tool over alternatives.

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