thruk_schedule_downtime

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

The description mentions accepted time formats ('now', relative, ISO 8601) but omits other behavioral traits like permissions required, return value, or side effects. Without annotations, more detail is needed.

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 very concise at 17 words, but efficiency compromises informativeness. It could be expanded without losing structure.

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 9 parameters and no output schema, the description is too sparse to guide an agent effectively. It lacks details on how to construct a downtime, what success looks like, and error conditions.

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 only 22%, and the description adds no parameter explanations beyond time formats. Parameters like fixed, author, comment, and duration_minutes are left 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?

The description clearly states the tool schedules downtime for a host or service. However, it does not differentiate from sibling tools like thruk_schedule_hostgroup_downtime or thruk_schedule_servicegroup_downtime.

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?

No guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The description merely states what it does without context.

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