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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, and the description adds genuinely new context: no credit cost ('free'), the full set of possible statuses, and that results are ranked 'best first'. It omits pagination behavior and what happens when no leads exist, but the safety profile and result semantics are covered well enough to act on.

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 tight sentences: return payload first, then the usage-relevant status hint. No filler. The trailing 'Read-only and free' is partially redundant with annotations, but 'free' still carries cost information not present elsewhere.

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?

There is no output schema, so describing the returned fields was this description's job, and it does that competently (post content, lead rationale, draft, status). Gaps remain on result volume/pagination given the `limit` maximum of 200 and on the full status set, but nothing critical to a correct call is missing.

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 coverage is 60% (brand_id, user_goal, connection_id are documented in-schema; status and limit are not). The description explains the meaning of `status: "new"` and the ordering, which is real added value, but it lists only new/posted/dismissed/failed while the schema enum also contains `approved`, and it says nothing about `limit`, `user_goal`, or `connection_id`.

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 ('reply leads found for this brand') and enumerates the record shape returned: public post link/text/author, lead reason, drafted reply, status. That is unambiguous about what the tool does. It never names or contrasts with the obvious sibling `find_reply_leads` (or `list_review_queue`), so differentiation is left to 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?

Gives concrete selection context: `status: "new"` returns the items waiting on the user, ordered best first, which is the primary invocation pattern. It stops short of exclusions or naming alternatives — nothing says when to prefer `find_reply_leads` or when to follow up with `approve_reply_lead`/`dismiss_reply_lead`.

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