N1Mm Clock

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

No annotations are provided, so the description carries the full burden, and it discloses nothing behavioral: no hint that it is a read-only view, no mention of what pacing assumes, no note on how off-time is computed from min_gap_minutes. An output schema exists, which relieves some return-value burden, but the behavioral profile is essentially absent.

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?

A single short clause with no wasted words and the core resource front-loaded. It is arguably too terse to be useful rather than padded, so it sits at 4 rather than 5.

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?

For a tool with five parameters, an output schema, and eight siblings, one sentence is not enough. The description never says the tool works with zero arguments (all params optional), nor distinguishes the pacing view from other state-reporting tools, leaving the agent to guess when to call it.

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 description coverage is 100% and each of the five optional parameters is documented in the schema itself, so the baseline of 3 applies. The description adds no extra meaning about how target_qsos/target_score/duration_hours interact or what happens when they are omitted.

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?

Names the resource (contest clock) and three facets it covers: timing, off-time, pacing. But it uses no verb (get/return) and 'in one view' is filler that doesn't tell the agent what it actually receives. It is distinguishable from n1mm_performance or n1mm_current_state only by inference.

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 indication of when to use this versus the other eight N1MM siblings, several of which (n1mm_current_state, n1mm_performance) plausibly overlap with timing/pacing. No prerequisites, exclusions, or contest-session context stated.

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