Bind Map Frame

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

Annotations already cover the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=false). The description adds two pieces of context beyond that: the binding is 'explicit' and a URI is read back for verification, which hints at a confirmable/idempotent mutation. It does not say whether an existing binding is overwritten, what happens on failure, or whether the project must be saved.

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?

It is a single compact sentence with the action front-loaded and no filler. It is efficient, though the brevity is partly the cause of the semantic gaps noted elsewhere.

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 mutation tool that binds a layout element to a map, the description omits preconditions, overwrite behavior, and any note on the returned URI even though an output schema exists. The output schema excuses return-value prose, but the missing operational context leaves it inadequate for confident invocation.

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 all four required parameters (aprx_path, layout_name, mapframe_name, map_name) are documented only by their titles. The description does not explain any of them, such as the expected path format for aprx_path or how names are resolved, so it fails to compensate for the coverage gap.

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 states a specific verb ('绑定' / bind) and resource ('布局地图框' / layout map frame) plus the target ('地图' / map), which cleanly separates it from siblings such as list_layout_map_frames, mapframe_extent, or set_mapframe_extent. It is clear but never names or contrasts an alternative sibling, so it falls short of a 5.

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 statement of when this tool should be used instead of alternatives, no prerequisites (e.g. project/layout must exist, view state), and no exclusions. For a among ~250 sibling tools in the layout/mapframe family, a 'when to use' cue is especially valuable and is entirely absent.

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