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

With no annotations, the description carries the full burden. It conveys a read-only operation via 'Get' but does not disclose edge-case behaviors such as what happens when no Mod Jam is active, whether it returns time in seconds/minutes, or if it could error. The tool is simple, but these missing details prevent a higher score.

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 with no redundant words. It efficiently states exactly what the tool does and earns its place without any 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?

With no output schema, the description should describe the return format (e.g., seconds, formatted time, or null if no jam). It fails to mention units or behavior in edge cases, leaving a significant completeness gap for such a simple 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 tool has zero parameters, so the input schema is trivially fully covered. The description adds no parameter information because none is needed. Per the rubric, a baseline of 4 applies for tools with no parameters.

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 'Get time remaining in the current Mod Jam' uses a specific verb ('Get') and clearly identifies the resource (time remaining) and scope (current Mod Jam). It distinguishes itself from siblings like jam_status and game_jam_theme by focusing on the countdown aspect.

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: you call it when you need the time remaining in the current Mod Jam. However, it provides no explicit guidance on when to prefer this over related tools (e.g., jam_status) or any exclusions, so it's only implied rather than explicitly stated.

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