get_upcoming_sdts

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

Annotations already establish readOnlyHint, idempotentHint, and non-destructive behavior, so the description does not need to repeat safety traits. It adds value by clarifying the temporal semantics ('scheduled to start'), but it does not disclose ordering, timezone handling, pagination, or what exactly defines the window boundary.

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 with no filler. Every word contributes to the core meaning, and the key temporal constraint is stated up front.

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 simple read-only tool with two optional documented parameters and strong safety annotations, the description is mostly sufficient. Minor gaps remain around timezone/relative-now semantics and result ordering, but these are unlikely to prevent correct 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 coverage is 100%, with both parameters already described ('Max results' and 'Hours ahead to look'). The description's 'time window' wording loosely connects to hours_ahead but does not add meaningful detail beyond what the schema already provides.

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 ('Get'), a clear resource ('SDTs'), and a distinct selection predicate ('scheduled to start within a time window'). This differentiates it conceptually from siblings like list_sdts and get_active_sdts, though it does not explicitly name those alternatives.

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 phrase 'scheduled to start within a time window' implies this is for upcoming SDTs, giving some usage context. However, it does not explicitly state when to choose this over list_sdts, get_active_sdts, or get_scheduled_downtime_jobs, nor does it mention any exclusions.

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