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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real value beyond them: returned field names (replyWindow.open, closesAt, canReply), the platform-specific 24-hour reply rule for Instagram/Messenger/WhatsApp, and an explicit prompt-injection warning about message text from outside the workspace. It does not describe error behavior or pagination beyond the count limits.

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 sentences, front-loaded with the 'Read only' safety framing, and every sentence carries information the schema or annotations do not. The middle sentence is long and parenthetical, bundling three return fields with a platform rule, which slightly hurts scanability but does not waste words.

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?

No output schema exists, and the description compensates by naming the key response fields and the meaning of canReply/closesAt, plus a trust-boundary warning for external content. For a simple two-parameter read tool this is close to complete; only error or empty-conversation behavior is left unstated.

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?

With schema description coverage at 100%, the schema already documents both parameters, including the default of 20 and the pointer to postfjord_list_conversations for conversationId. The description adds the 50-message cap and the 'oldest first' ordering semantics, but otherwise restates what the schema provides, 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?

The description states a specific verb (Read) and resource (the latest messages in ONE Inbox conversation), and pins down ordering ('oldest first') and volume bounds, plus the secondary payload (replyWindow, canReply). 'One Inbox conversation' implicitly separates it from a conversation-listing tool, so an agent knows this is a single-thread retrieval rather than a browse.

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?

Usage is only implied: the reply-window and canReply explanation hints that this tool is for checking whether a reply can go out, which routes toward draft_reply-type tools. However, no alternative is named and there are no explicit when-not conditions, so the agent must infer the boundary from context rather than being told.

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