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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and closed-world, but the description adds nothing beyond that: it does not say the view change is applied immediately to the user's live session, whether it persists for saved maps, or how drafts behave. For a state-mutating view tool with zero added behavioral context, this is a real gap.

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 five-word sentence with no filler, so nothing is wasted, but it is under-specified rather than economical. Front-loading is fine; the problem is that the sentence carries almost no 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?

For a tool with six parameters, a required map_id plus a one-of targeting constraint, draft support, and no output schema, the description is far too thin to guide correct invocation. Nothing explains what a successful move returns or how the required targeting choice interacts with drafts.

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?

With 6 parameters and only 50% schema description coverage, the description needs to compensate and does not. It says nothing about center-vs-place exclusivity, the lat/lng vs address vs place_id center variants, the zoom bounds (3-16), draft_handle for unsaved maps, or conversation_id.

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 concrete verb pair ('Pan/zoom') and a concrete resource ('the live map'), so an agent can tell this moves the viewport rather than editing places or lists like the sibling tools do. It stops short of naming any sibling or clarifying whether 'live map' includes unsaved drafts.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives such as map_get_state (reading the view) or map_update (changing map metadata). The agent must infer from the name alone that this is the viewport-navigation tool.

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