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

Beyond the annotations, the description discloses that execution is asynchronous, that later runs suppress posts already listed by earlier runs, that drafts are produced for the user to post, and that nothing is published on the user's behalf. That last point meaningfully reinforces destructiveHint=false. There is a mild tension: 'the same request again returns its progress or the finished list' sounds close to idempotent, while idempotentHint=false declares otherwise, though this reads as a polling affordance rather than a real contradiction.

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?

The core explanation is front-loaded and reasonably tight, but the structure is jumbled: parameter glosses are dropped mid-paragraph, then the text returns to the polling behavior. 'Puley posts nothing' arrives as an unexplained brand reference, and one sentence is missing an article, which makes the text slower to parse than it needs to be.

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 an asynchronous, no-output-schema job, the description covers the essentials: what triggers it, what it produces, that it runs in the background, and how to retrieve results by re-calling. It does not say where or in what shape the finished list arrives, how long a run typically takes, or what happens if no matching posts are found.

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 0%, so the description carries the full burden of explaining the parameters, and it gives only thin glosses: 'what: what is sold' and 'offer: a line about the person's offer.' It does not say how granular 'what' should be, or how long 'offer' should be, or what the empty default means. An agent can guess, but the semantics remain underspecified.

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 names concrete verbs and resources: finds posts on Reddit and X where people ask for what the user sells, and drafts a first reply for each. That is far more specific than the tool's name 'new_buyers' and lets an agent distinguish it from read-only search siblings like search_posts or people_asking. It never explicitly says which sibling to prefer, though, so it stops short of a 5.

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?

It gives useful invocation context: it runs once in the background, and calling again returns progress or the finished list. That effectively tells the agent not to re-invoke to poll for new work. It never says when to choose this over the many related research or search siblings, and it never states prerequisites, such as whether Reddit or X accounts must be connected first.

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