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

Annotations already cover read-only, idempotent, non-destructive behavior, so the bar is lower. The description nevertheless adds real value beyond them: result ordering (most recent bot reply first), per-conversation reply counts, enforcement of the organization's MCP conversation scope (channel allowlist, label scope, group toggle), and the required read_bots and read_conversations permissions. Pagination behavior is the only notable gap.

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?

Three tight sentences: what it returns and how it is ordered, what constrains the results and what auth is needed, then the alternative tool. Nothing is redundant and the core scope statement is front-loaded.

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 an output schema present, return values need not be described, and the description covers ordering, permissions, scope filtering, defaults, and the sibling alternative. Only paging mechanics (limit/cursor) are left unaddressed for a tool that clearly paginates.

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 carries the full burden. It fully explains the days parameter (range 1-30, default 30), but says nothing about limit (1-50 cap), cursor-based paging, or the bot_id 'default' vs numeric-id pattern. Partial compensation across four undocumented parameters warrants a middling score.

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 gives a specific verb and resource with precise scope: conversations a bot has replied in over the last N days, ordered by most recent bot reply, with reply counts. This is clearly distinguishable from list_conversations (all conversations) and get_bot_transcript (the actual exchange), which the description explicitly routes to.

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?

It names an explicit alternative for the adjacent need ("Use get_bot_transcript for the exchange") and states the selection condition (bot must have replied within the window). It does not explicitly contrast with list_conversations, but the 'bot has replied in' scoping implicitly separates them.

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