thruk_unacked_critical

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

No annotations provided. The description indicates it's a read operation (non-destructive) and mentions the time threshold, but lacks details on return format, permissions, or pagination. Adequate for a simple list tool but could be more transparent.

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?

Single sentence, 13 words, no fluff. All essential info is front-loaded. Every word serves a purpose.

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?

No output schema, so the agent doesn't know the return format. Despite clear purpose and well-documented parameters, the lack of output details leaves some uncertainty. Adequate for a simple tool but could be more complete.

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 detailed descriptions for all parameters. The tool description adds context about the threshold (N minutes) but not much else. Baseline 3 is appropriate as the schema carries the information.

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 retrieves CRITICAL services and DOWN hosts that are not acknowledged for a specified duration. It uses a specific verb (implied 'list') and resource ('unacknowledged critical items'), which distinguishes it from siblings like thruk_problems or thruk_stale_acks.

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 implies usage: when you need unacknowledged critical issues older than N minutes. While not explicitly stating alternatives, it gives clear context for when to use this tool over others. A brief mention of exclusions would elevate it.

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