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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false). The description adds genuinely useful behavioral context beyond that: results are grouped by counterpart, and the counterpart's contact is only revealed once an offer is accepted — a conditional disclosure an agent would not otherwise know.

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 sentences with zero filler. The primary action and scope are front-loaded in the first sentence, and the second adds a conditional behavioral detail. Every word earns its place.

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 annotations carrying the safety profile and the description covering the grouping and conditional contact behavior, the core picture is adequate. However, there is no output schema and no description of return shape details (message fields, ordering, empty-state behavior) or error cases like an invalid owner_token, leaving notable gaps for a 2-param tool with 0% schema coverage.

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% for the two parameters, so the description must compensate, but it only loosely maps to them: 'for your post' hints at post_id and ownership, yet owner_token's role (authentication/authorization) is never explained. The description adds minimal meaning beyond the bare schema.

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'), a precise resource ('all negotiation threads for your post'), and a distinguishing behavior ('grouped by counterpart'). It clearly differentiates from siblings like send_message (write operation) and get_post (single post view), so an agent can tell it apart without inspecting other schemas.

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 scope 'for your post' conveys the core condition for when this tool applies to read negotiations, but no alternatives are named and no when-not-to-use guidance is given. Usage context is implied rather than explicitly routed away from siblings like search or get_post.

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