Sdk Set Active 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 operation. The description adds meaningful behavioral context beyond the annotations: passing empty start/end disables time rather than erroring, and the time range is offset-aware. It still omits required-session behavior and error conditions.

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?

One compact sentence that front-loads the operation and then states the empty-input behavior. There is no filler and the essential info comes first.

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 mutating tool with six parameters, three required identifiers, no schema descriptions, and a confirmation flag, the description is materially incomplete. It does not explain the session/map/generation references or confirm semantics, though the existence of an output schema reduces the need to describe return values.

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%, so the description carries the full burden for six parameters. It only clarifies the semantics of start_time and end_time (empty both disables time) while leaving sdk_session_ref, expected_map_uri, expected_context_generation, and confirm entirely unexplained.

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 and resource: set the offset-aware time range of the native active MapView. The scope (active MapView) helps distinguish it from general view tools, but it does not differentiate itself from sibling time tools such as set_time_slider, layer_enable_time, or set_mapframe_time.

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 concrete usage condition: when both start and end are omitted, time is disabled. However, it provides no guidance on when to choose this tool over other time-related siblings, and no prerequisites or exclusions are stated.

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