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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds that mentions are delivered by webhook and that the result shape matches list_conversations, which is useful context. It does not go further into auth requirements, rate limits, or pagination, but for a read-only list tool this is acceptable.

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 sentences, no wasted words, and the core purpose is front-loaded. The mention of same-shape and the send_dm follow-up both earn their place by giving the agent actionable orientation.

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 required parameters and readOnlyHint=true, the tool is simple enough that the description covers the main context: what is listed, how it relates to list_conversations, and what to do with the results. There is no output schema, so the 'same shape' reference is important and mostly sufficient, though unread semantics remain unexplained.

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 only 33%, with workspaceId described in the schema but accountId and unread left undocumented. The description does not compensate for this gap: it never mentions unread, accountId, or how they affect the results. The 'same shape as list_conversations' line is too indirect to clarify parameter behavior.

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 clearly states what the tool does: it returns Threads posts that mention the connected account. It also distinguishes itself from list_conversations by noting it is the same shape but filtered with kind mention. This is enough for an agent to understand its specific role among many list tools.

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 reference to list_conversations implies when this tool is appropriate, and 'Reply with send_dm' gives a useful follow-up action. However, it does not explicitly state when not to use this tool or compare it against other list alternatives like list_posts or list_channel_posts. The usage context is implied rather than explicit.

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