Set Time Slider

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

Annotations already cover safety traits (not read-only, idempotent, non-destructive), but the description adds an important limitation: ArcPy cannot control the active MapView time slider. That is useful behavioral context beyond the annotations, though it still does not describe the tool's actual side effects.

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 short, front-loaded, and free of filler. It quickly states the compatibility status and then gives the routing alternatives.

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?

The output schema exists, so return values need not be explained, and annotations cover safety. Yet for a six-parameter mutating tool with 0% schema description coverage, the description omits parameter semantics and the precise behavior of the tool itself.

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 says nothing about any of the six parameters, including required ones such as aprx_path, map_name, and layer_name. With no schema descriptions and no compensating detail, the parameter meanings are undocumented.

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 identifies this as a compatibility alias for layer time enablement and distinguishes it from arcgis_pro_set_mapframe_time and the SDK bridge. However, it does not clearly state what calling this tool actually does, especially given the name suggests controlling a time slider while the text says ArcPy cannot control the active MapView time slider.

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?

It explicitly names alternatives and the contexts for them: use arcgis_pro_set_mapframe_time for a layout map frame or the SDK bridge for the live MapView. But it never states when this tool itself should be used, leaving its appropriate use case implicit.

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