arcgis_zoom_to

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

Discloses that the tool causes visual map movement and can optionally select features first. Without annotations, description carries full burden and adequately covers the visible effect.

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: two sentences covering main action, optional behavior, and prerequisite. No wasted words, front-loaded with purpose.

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?

Given simple tool (2 params, no output schema), description adequately explains both usage modes and a key prerequisite. Could mention error cases but not necessary for a zoom tool.

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% (baseline 3), but description adds extra detail: explains the where behavior as 'first selects matching features then zooms to the selection', which adds semantic value beyond schema.

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?

Description clearly states the verb ('zoom to') and resource ('active map view to a feature layer'). It distinguishes from sibling tools which have different purposes (export, query, run geoprocessing, etc.).

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 explicit prerequisite ('requires Pro to be in map view, not layout') and explains the optional where condition behavior. Does not explicitly contrast with siblings but contextually differentiation is clear.

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