get_scheduled_downtime_jobs

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description does not need to repeat those. However, it does not disclose what the tool actually returns (e.g., a list of scheduled downtime jobs) or any other behavioral traits. The phrase 'SDT automation' is unclear and adds little beyond the name.

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 one sentence, which is concise, but it is under-specified. It fails to convey the tool's purpose clearly, so brevity does not add value here. The sentence is not front-loaded with the most critical information because the core function remains ambiguous.

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 no output schema, the description should clarify what the tool returns, but it does not. It also does not differentiate from many sibling get_* tools. Given the ambiguity around 'SDT automation' and the lack of output details, the description is incomplete for an agent to correctly select and use the tool.

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?

The schema covers the single 'limit' parameter with a description ('Max results'), so the schema carries the full burden. The description adds no additional parameter context, but with 100% coverage, a baseline of 3 is appropriate.

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 verb ('Get') and a resource ('batch jobs related to SDT automation'), but 'related to SDT automation' is vague and ambiguous. It does not clearly specify that this returns scheduled downtime jobs, nor does it distinguish from get_batchjobs or get_device_batchjobs. It is not a tautology but lacks precision.

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?

There is no guidance on when to use this tool versus alternatives such as get_batchjobs, get_batchjob, or get_device_batchjobs. No exclusions or context are provided, leaving the agent to infer usage from the name alone.

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