setView

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

Describes instantaneous behavior and lack of animation, consistent with annotations idempotentHint=true. Does not detail side effects or state changes beyond camera position, but adequate for a simple tool.

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?

Extremely concise single sentence with no wasted words. Front-loads the core purpose and key differentiator (no animation).

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?

Adequate for a simple tool with well-documented parameters. However, does not explain scope of effect (e.g., whether other layers are affected) or confirm that only camera changes, which could be inferred from idempotentHint.

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?

All 7 parameters have descriptions in the schema (100% coverage). The description adds no extra information about parameter semantics beyond what schema provides.

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?

Clearly states action 'switch', resource 'view', and key parameters 'longitude/latitude'. Distinguishes from sibling tools like flyTo (animation) and getView (retrieval).

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?

Implies usage for instant jumps without animation compared to flyTo, but lacks explicit guidance on when to use this vs alternatives. Does not mention prerequisites or limitations.

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