Sdk Context

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value by enumerating the specific context fields retrieved, but it says nothing about session requirements, freshness, or failure behavior beyond that.

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 the verb first and no padding. The enumeration of returned items is dense but every element carries information.

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?

Since an output schema exists, return values need not be explained, and the annotations cover safety. The main remaining gap is the undocumented required session parameter, which is important for a call whose only input is the session handle.

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 single required parameter sdk_session_ref is undocumented in both schema and description. The description does not compensate for this gap, leaving the meaning and valid source of the session reference implicit from the parameter name alone.

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 uses a clear read verb and enumerates the specific resources it returns (active view, camera, active layers, selection summary, time, CAS generations), so an agent can tell what it fetches. However, it does not differentiate itself from overlapping siblings such as arcgis_pro_active_view_info, arcgis_pro_map_camera, or arcgis_pro_window_status.

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 indication of when to use this consolidated context read versus the more granular sibling tools, and no prerequisites or exclusions are stated. The only implied guidance is that it is a read operation.

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