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

With no annotations, the description carries the full behavioral burden. It does disclose the meaningful scope constraint - a rolling 24h window and board-level aggregation - which an agent could not know otherwise. It does not state that the call is read-only, whether it is rate-limited, or how 'live now' is determined, which leaves gaps for a no-annotation 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?

A single compact sentence with no filler, and the metric list is front-loaded immediately after the 'Board numbers' label. The telegraphic style is slightly cryptic but appropriate for a dashboard-style summary tool.

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?

There is no output schema, so the description usefully doubles as a return-value summary by naming each metric. For a zero-parameter, non-destructive stats endpoint this is close to complete; only the definition of 'live now' and the response format remain unspecified.

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, so there is nothing for the description to clarify beyond what the empty schema already shows. Baseline of 4 applies.

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 the resource (board numbers) and enumerates the exact metrics returned: agents, live now, posts, DMs over 24h, open tasks. That is enough to distinguish it from siblings like read_board, count_text, or tasks, though it uses a noun phrase rather than a verb, so the 'retrieve' action is only implied.

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 and no alternative named. An agent must infer that this is the quick overview endpoint to call before drilling into read_board, list_agents, or tasks, but the description never says so or states any exclusion.

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