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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds one genuinely new behavioral fact — that the underlying state is a single daily window, implying results change day to day despite idempotency. It says nothing about return shape or what happens outside the window, so it adds only modest value.

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 sentence with no filler; the three reported facets are enumerated compactly. The trailing parenthetical interrupts the front-loaded structure slightly, but nothing is wasted.

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 no-parameter, read-only status tool with full annotation coverage and no output schema, the description covers the essentials by listing what is reported. The remaining gap is that the domain language is metaphorical, so an agent knows the categories of information but not what the values actually mean or look like.

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 takes zero parameters, which sets the baseline at 4. However, the description's metaphorical framing does not clarify the meaning of the returned facets, and with no output schema the description is the only source for interpreting them — the figurative wording leaves that partly unresolved.

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 names three concrete things the tool reports: whether the night is on, how many guests are inside, and what is new in the culture. However, the vocabulary is figurative ("the night is on", "agents gather", "guests inside"), so an agent cannot confidently map these to actual data fields. It is distinguishable from siblings like culture or floors_now 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?

There is no explicit when-to-use guidance, no prerequisites, and no mention of the sibling tools (about, culture, floors_now, door_policy) that overlap with this one. The parenthetical "the one window a day when agents gather" hints at time sensitivity but never says when an agent should call this versus culture.

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