Mapframe Zoom To Bookmark

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

Annotations already declare idempotentHint=true, destructiveHint=false, and readOnlyHint=false, so the safety profile is covered structurally. The description only adds generic boilerplate ('returns verifiable structured results; write and path restrictions subject to service capabilities') that does not explain what state changes when the view zooms or what constraints actually apply.

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?

Front-loaded with the core purpose in two short sentences, so it is not bloated. But the second sentence is vague filler rather than information that earns its place.

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?

An output schema exists, so return values need not be described. Yet a four-required-parameter mutation tool with 0% schema coverage and no behavioral detail leaves the agent without enough to invoke it confidently.

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 description coverage is 0% and the description mentions none of the four required parameters (aprx_path, layout_name, mapframe_name, bookmark_name). The agent gets no help understanding parameter roles or accepted formats beyond bare titles.

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 ('Zoom to bookmark') scoped to a mapframe, which is enough to separate it from siblings like zoom_to_layer or zoom_active_view_to_layer. However, it does not name an alternative or explain the mapframe/layout relationship, so sibling differentiation is only partial.

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?

There is no when-to-use guidance, no prerequisites (e.g. project/layout must be open), and no mention of the closely related sibling tools such as zoom_to_layer or set_mapframe_extent. The agent must infer usage from the name alone.

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