flyTo

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

Annotations already declare non-destructive, idempotent, and non-read-only hints, so the bar is lower. The description adds that it animates (implying state change) and returns a structured object with success/error, but doesn't provide further behavioral detail like whether it interrupts previous animations or affects other entities. It meets minimum adequacy but adds limited context beyond annotations.

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?

The description is three concise sentences: purpose, usage, and return type. It is front-loaded with the core action, uses no filler, and every sentence adds value. It's an exemplar of minimal yet informative documentation.

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?

Despite having 7 parameters, the tool is straightforward—animate camera to a location with optional adjustments. The description covers the action, when to use, and return shape. The schema fully documents parameters, and no output schema is needed since the description states the return object. For a simple camera animation, this is complete.

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 100% with each parameter having a description. The description doesn't add any parameter-specific information beyond what's in the schema, but it does mention the return object structure (success/message/error). With full schema coverage, a baseline of 3 is appropriate; the description neither adds nor detracts from parameter understanding.

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 clearly states the tool animates the camera to a geographic location, distinguishing it from sibling tools like setView (likely non-animated) and zoomToExtent (based on extent). It specifies the verb 'animate' and the resource 'camera' with geographic targeting, making the purpose unambiguous.

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?

The description provides clear guidance: 'Use for visible navigation requested by the user.' This implies it's for explicit user-requested camera movement, differentiating from programmatic or default navigation. However, it doesn't name specific alternatives or exclusionary cases, though the sibling list indicates similar tools exist.

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