Set Mapframe Time

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

Annotations already declare this as a non-readonly, idempotent, non-destructive mutation. The description adds which mapframe time properties are changed, but does not mention persistence, save requirements, or whether the layout must be open. No annotation contradiction.

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?

A single, front-loaded sentence that names the action and the specific settings affected. No filler or redundancy.

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?

With output schema and annotations present, the description does not need to cover return values or safety. However, for a 7-parameter mutation tool with no schema descriptions, it is only minimally complete: it omits usage guidance and does not document the three required parameters.

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% across 7 parameters, so the description must compensate. It explains enabled (MapTime switch), start_time/end_time as ISO-8601, and time_inclusion as endpoint inclusion, but leaves the required aprx_path, layout_name, and mapframe_name parameters unelaborated.

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 clear verb+resource+key properties: setting a layout mapframe's MapTime switch, ISO-8601 start/end times, and time inclusion. It is more specific than the title alone, but it does not explicitly distinguish the tool from the sibling query tool arcgis_pro_mapframe_time_info.

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 gives no when-to-use guidance, no prerequisites, and no comparison with alternatives such as arcgis_pro_mapframe_time_info or arcgis_pro_set_time_slider. It only restates the operation.

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