room_metrics

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only aggregate but says nothing about permissions needed, whether metrics are computed live or cached, or any rate/latency characteristics; only the metric dimensions themselves are disclosed.

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?

One terse, front-loaded fragment with no filler; the metric dimensions are listed compactly. It is efficient, though it reads as a label rather than a sentence, which slightly limits clarity.

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?

An output schema exists, so return shape need not be explained, and the description usefully previews the metric categories. However, with no annotations and an undocumented room_id, an agent still lacks permission context and identifier semantics needed to call it confidently.

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 single parameter room_id has 0% schema description coverage and the description adds nothing about which room identifier is expected or how it is obtained. With coverage this low, the description should compensate, and it does not.

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 (activity metrics) and enumerates the three measurements returned: messages per agent, type breakdown, task completion. That is enough to distinguish it from read siblings like get_room_state or list_participants, though it never explicitly says which sibling to prefer.

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 statement of prerequisites, and no mention of alternatives among the many room-scoped siblings. The agent must infer that this is the analytics view of a room rather than a state or membership view.

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