Sdk Refresh View

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

The annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the agent knows this is a non-destructive but non-read operation. The description adds genuinely useful behavioral context beyond that: it is a blocking call that waits for the subsequent DrawComplete event or explicitly reports a timeout. It does not explain what confirm/clear_cache affect or what state the redraw mutates.

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 front-loaded sentence with no filler; the redraw action and the wait/timeout semantics are stated immediately. It is tight, though arguably too terse for a 6-parameter SDK 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, but for a blocking 6-parameter SDK call the description omits session/generation semantics, what clear_cache destroys, when to use this versus refresh_layer, and timeout consequences. Too thin relative to the tool's complexity.

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 6 parameters (3 required), so the description must carry the burden and largely fails. Only faint hints exist: '同一地图' loosely implies the expected_map_uri matching and the timeout wording loosely implies wait_milliseconds, but sdk_session_ref, expected_context_generation, confirm and clear_cache are never addressed.

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 states a specific verb+resource ('请求原生 MapView redraw' – request a native MapView redraw) and adds the distinctive behavior that it waits for DrawComplete. That distinguishes it from data-oriented siblings like refresh_layer. It does not, however, name any sibling or scope itself against them explicitly.

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 guidance on when to prefer this over alternatives such as arcgis_pro_refresh_layer or arcgis_pro_refresh_map_series, nor any prerequisites. The agent must infer usage entirely from the verb.

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