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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description adds meaningful behavior beyond that: default returns up to 100 threads, ordering is most-recent-first, and the no-inbox case is not an error and is created on first inbound message. This is useful context the annotations do not provide.

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?

Four sentences with the core purpose front-loaded, followed by return row fields and edge cases. Every sentence contributes real information; the only slight inefficiency is the final sentence about inbox creation, which is useful but could be seen as extra.

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 simple read-only list tool with one optional parameter and no output schema, the description covers the essential return fields, ordering, default scope, maximum threads, duplicate-brand threads, and the empty-inbox behavior. It doesn't explicitly explain the limit parameter's mechanics, but the tool is simple enough that this is not a major gap.

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 for the lone optional limit parameter. It says 'whole inbox by default (up to 100 threads),' which hints at the maximum but never explicitly explains that limit controls the number of returned threads or how it interacts with the default. This is partial compensation only.

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 identifies the resource ('creator's brand chat inbox') and the action (list threads, most recent activity first). It does not explicitly name split_read_conversation as the alternative, but says each row contains channel_url 'for reading and replying,' which makes the list-vs-detail distinction clear enough for an agent.

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 provides clear context for when to call this tool: when you need the overall inbox with recent activity, default whole inbox, up to 100 threads. It doesn't explicitly state when not to use it or name alternatives, but the list/read distinction is implicitly conveyed and the default behavior is well specified.

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