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

With no annotations, the description carries the full burden and does disclose the key trait: the camera is session-only and does not write the TS, with configure_map named for persistence. It also states the prerequisite. It stops short of covering failure behavior, unspecified-field handling, or permissions, so it is strong but not exhaustive.

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?

Dense but front-loaded: the 'When', prerequisite, and alternatives come in a logical order and each sentence routes the agent. Minor waste in the jargon header ('Tier 2 — Low-Level MC State') and the trailing 'Scenarios: residual backlog' line, which adds little.

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?

For a 7-parameter tool with only one required param and an output schema present, the description is nearly complete: it covers the primary mutable fields, the session-scoped semantics, and the alternatives. The only real gap is the undocumented guidance_handle, and return values need not be described given the output schema.

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 coverage is 0%, so the description must compensate, and it adds genuine meaning beyond the schema: center is a [longitude, latitude] pair and zoom is bounded 0-24, neither of which the schema states. It covers mode, active TAL, pending job ref, center, zoom, and map_session_id, but leaves guidance_handle entirely 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?

States a specific verb+resource (set MC map state) and enumerates exactly what it controls: MC mode, active TAL, pending job ref, and camera jump via center/zoom. It explicitly distinguishes itself from configure_map (durable persistence) and request_part_selection, so an agent can place it among siblings without opening schemas.

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?

Provides an explicit 'When:' trigger list, a prerequisite (map_session_id), and two named alternatives with the condition that selects them ('Prefer configure_map for durable TS map_config', 'Prefer request_part_selection for selection workflows'). Routing guidance is unusually complete.

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