Layer Enable Time

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds a useful scope clarification that it does not affect the MapView time slider, but does not disclose what project files are modified, required permissions, or whether changes persist across saves. With annotations carrying the main behavioral load, this is adequate but minimal.

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 a single front-loaded sentence with no wasted words. It efficiently conveys the core action and a key non-effect. However, for a tool with 8 parameters and a mutation operation, the extreme brevity borders on under-specification rather than pure conciseness.

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 the tool's complexity (8 parameters, mutation behavior) and the schema's 0% description coverage, the one-sentence description is far from complete. Although an output schema exists, the description does not cover required parameters (aprx_path, map_name, layer_name), optional time-field parameters, or the persistence implications of enabling/disabling time. Critical context is missing.

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 no parameters at all. With 8 parameters including enabled, start_time_field, end_time_field, time_dimension, and auto_calculate_time_range, the description fails to explain their meaning, defaults, or interactions. Parameter semantics are entirely absent.

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: enable/disable layer time properties. It distinguishes from the MapView time slider, which is a key sibling concern. However, it does not specify that it operates on a layer within a specific map of an aprx, nor does it clarify what 'time properties' concretely means (e.g., start/end time fields), leaving the purpose slightly broad.

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 a when-not boundary by stating it does not control the active MapView's time slider, which helps avoid misuse. But it provides no positive guidance for when to use this tool versus alternatives like arcgis_pro_set_time_slider or arcgis_pro_set_mapframe_time, nor does it name those alternatives explicitly. Usage is only implied.

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