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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the useful behavioral detail that the response mixes two entity types (guest activity and document view counts), which is not encoded anywhere else. It says nothing about pagination, limits, or whether empty rooms return empty arrays.

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?

It is a single tight fragment with no filler, which is good, but it is grammatically incomplete and not front-loaded with a verb, leaving the action implied. Efficiency is high but structure is weak.

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?

With no output schema, the description carries the burden of describing returns, and it does partially by naming guests, views, last visit, and document view counts. It omits the required identifier and any scoping or volume behavior, so an agent still cannot call it confidently from the description alone.

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 data_room_id has 0% schema description coverage, and the description never mentions it, so it does not tell the agent that a data room identifier is required or what it refers to. With one undocumented required parameter, the description fails to compensate for the schema gap.

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 a specific resource and enumerates what is returned: guests with their views and last visit, plus documents with view counts. That distinguishes it from siblings like get_document_stats, list_recent_views, and list_documents. It lacks an explicit verb ('Retrieve...'), which keeps it just short of a 5.

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 guidance on when to call this versus alternatives such as list_recent_views, get_document_stats, or list_data_rooms. The agent must infer from the content listing alone that this is the per-room activity rollup.

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