KBK Next Drop

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

With no annotations, the description carries the burden. It discloses that the tool returns a single event and includes a human countdown, which adds useful behavioral context. However, it does not mention what happens when there is no scheduled event, error behavior, or confirm it is read-only, leaving some gaps for a getter tool.

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 a single, front-loaded sentence that efficiently conveys the purpose, output, and use case. Every word earns its place with no redundancy or filler.

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?

Given the tool's simplicity (no params, no output schema), the description provides enough to understand what to expect: a single upcoming slot with a countdown. It lacks details on return format or edge cases like no upcoming drop, but for a low-complexity tool, these are minor omissions. Sibling differentiation is moderately covered by the use case phrase.

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 tool has zero parameters, making schema coverage trivially 100%. Per the rubric baseline for 0 params is 4. The description adds no parameter-specific details (none needed), and does not distract from the tool's purpose.

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 identifies the tool as returning 'the single next scheduled event/slot' with a 'human countdown', which distinguishes it from siblings like get_schedule that likely return full schedules. The noun phrase effectively states the resource and output, satisfying the verb+resource criterion.

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 provides clear context ('for a quick what's coming up answer') but does not explicitly mention when not to use it or name alternatives (e.g., get_schedule). It implies the distinction via 'single next' and 'quick', but lacks explicit exclusions, so it falls short of a 5.

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