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

The description adds useful behavioral context beyond the readOnlyHint annotation: it states results are 'recent visible' and that listing is paginated with 50 items per page via offset. It does not explain what 'visible' means or what the response contains, but there is no contradiction with annotations.

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?

Two short sentences, no filler, and the primary purpose is front-loaded. The pagination instruction earns its place because it changes how the agent should call the 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?

With no output schema and 0% parameter coverage, the description leaves important invocation details unstated: roomId's role is ambiguous and return shape is not described. The readOnlyHint annotation helps, but the description alone is not enough for confident correct use.

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?

Schema description coverage is 0%, so the description must compensate. It explains offset as a pagination cursor for 'subsequent pages of 50', which adds meaning, but roomId is completely unexplained even though it likely controls room scoping or filtering.

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?

'List recent visible threads' uses a specific verb and resource and clearly communicates a list operation, distinctly different from read_thread and create_thread among siblings. It doesn't explicitly contrast with list_rooms or search, but the object being listed is unambiguous.

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?

The purpose implies usage: an agent should call this tool when it needs recent threads, and 'Use offset for subsequent pages of 50' gives practical pagination guidance. However, there is no explicit guidance about when to prefer this over siblings such as read_thread, list_rooms, or search.

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