Refresh Map Series

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the basic safety profile is covered. The description adds that it refreshes MapSeries index state and returns refreshed page information, which is useful context, but it does not disclose deeper behavior such as required permissions, project-open prerequisites, or side effects beyond the refresh.

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?

The description is a single front-loaded sentence with no wasted words. It is concise and easy to parse, though its brevity also means it omits important context that belongs in other dimensions.

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, and annotations cover the safety profile. However, with two required parameters at 0% schema description coverage and no usage guidance, the description leaves significant gaps for an agent selecting and invoking the tool 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% and the description does not mention aprx_path or layout_name at all. It therefore fails to compensate for the undocumented parameters, leaving their expected formats and relationship to the map series unexplained.

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 names a specific verb and resource: refresh MapSeries index state and return refreshed page information. It is clear what the tool does, but it does not distinguish itself from sibling map-series tools such as arcgis_pro_map_series_info, arcgis_pro_set_map_series_page, or arcgis_pro_export_map_series_pdf.

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?

The description gives no guidance on when to use this tool versus alternatives. It does not state prerequisites, when a refresh is needed, or how it relates to other map-series operations, leaving usage entirely to inference from the name.

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