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

readOnlyHint=true already tells the agent this is a safe read, and the description usefully adds the default ordering ('newest first') and the cross-account default scope. It says nothing about result truncation, the 50-item ceiling behaviour, or how the 'before' cursor interacts with ordering, which is the main behavioral risk when paging.

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?

A single sentence that front-loads the verb and resource, then packs scope and ordering into one parenthetical. No wasted words and nothing important buried.

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?

For a read-only, zero-required-parameter list tool with a fully documented schema and no output schema, the description covers what is listed, ordering, and account scope. The remaining gap is pagination semantics (how 'before' interacts with newest-first ordering and the 50-result cap), which an agent paging results would want.

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 100%, so every parameter (limit, query, before, account, channel, unread_only, include_hidden) is already documented in the schema with defaults and allowed values. The description only restates the account scope axis and adds no format or interaction detail beyond structured fields, so the baseline 3 applies.

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?

States a specific verb and resource ('List recent inbox conversations') and enumerates the conversation types covered (DMs, groups, channels, ticket threads), which clearly separates it from read_conversation or get_ticket. It does not explicitly name a sibling it supersedes or defers to, so the differentiation is implied rather than stated.

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 description establishes this as the browsing/listing entry point ('recent', 'newest first'), which implies when to reach for it, but never says when to use search_messages instead for text search or read_conversation for a single thread. No exclusions or prerequisites are stated.

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