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 corroborates this by naming the read endpoint (GET /conversations/{id}/posts) and notes the items are integration/app-generated, but adds nothing about pagination ordering, result size behavior, or auth scopes.

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 short sentences, with the purpose front-loaded ahead of the endpoint reference. Efficient, though the trailing 'Missive: GET /conversations/{id}/posts.' restates metadata that adds little for tool selection.

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 whose schema fully documents its three params, the description is adequate but thin: with no output schema, it does not describe the shape or contents of returned posts, nor how the cursor pagination behaves.

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%: id, limit, and the until cursor are all documented in the schema. The description adds no parameter meaning beyond the schema, so the baseline of 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 (List) and resource (posts on a conversation), and the parenthetical '(integration/app-generated items)' clarifies what a 'post' is, distinguishing it conceptually from conversation messages, comments, and drafts. It does not explicitly name those siblings, so the differentiation relies on the reader's inference.

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?

There is no guidance on when to use this rather than the sibling listers (conversation_messages, conversation_comments, conversation_drafts). Usage is only implied by the tool name; no exclusions or prerequisites are given.

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