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

With no annotations, the description carries the full burden of behavioral disclosure and provides essentially nothing: no indication of read-only behavior, no return shape, no pagination, no timezone handling, no explanation of how 'now' is bounded. It is not misleading, but it is behaviorally empty.

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 single sentence is short but under-specified rather than concise. Brevity without substance leaves no information to front-load, making the tool harder to invoke correctly.

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 six-parameter tool with no annotations, no output schema, and a crowded sibling set of event and place tools, one vague sentence is wholly insufficient. Nothing tells the agent what a live-now result contains or how it differs from get_events or get_happening_today.

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?

All six parameters have schema descriptions (100% coverage), so the schema carries the burden, and the description adds no parameter meaning on top. Baseline 3 is appropriate, though the schema's own descriptions for tz, limit, and offset are minimal.

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 is a question that essentially restates the tool name in sentence form: 'What is happening right now.' It hints at real-time events but names no specific verb or resource, and does nothing to distinguish it from siblings like get_happening_today, get_events, or get_live_now's obvious relatives.

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 when-to-use guidance, no prerequisites, and no mention of alternatives among the many sibling event/place tools. The agent is left to infer everything about when this tool is appropriate.

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