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

Annotations only say readOnly=false, openWorld=true, destructive=false; the description goes well beyond them by disclosing runtime (~2 minutes, background), cost (8 credits, charged only when drafts are written), a required human confirmation before charging, ranking/source constraints, and the reassuring 'Nothing is posted.' These are exactly the operational facts an agent needs before invoking.

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?

It is a single dense block with a broken opening clause ('Once a feature built from an idea is live: the run behind Assisted posts...') that reads awkwardly. It is information-rich and mostly front-loaded, but the two most actionable facts for an agent — the 8-credit cost and the wait-for-approval rule — are buried near the end.

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 no output schema, the description does state the return value (link to the drafts) and covers side effects, timing, cost, consent, and eligibility exclusions. The only real gap is what happens on failure or when no eligible posts are found, which is minor for a draft-generation tool.

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 50%: 'key' is documented as IDEA:<slug>, but 'platform' has no schema description. The description partially compensates by implying a single platform ('for one platform') and by explaining platform-specific behavior (X a week old at most, Reddit open threads and self-promotion rules), which adds real semantics to the reddit/x enum.

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 a concrete verb+resource: find candidate posts and write one reply each about a feature that shipped from an idea, returning draft links. It orients the agent by calling itself 'the run behind Assisted posts (the same as reach_find)', which effectively distinguishes it from the plain ideas_replies sibling. The prose is convoluted, but the scope (this idea, one platform, up to 5 replies) is unmistakable.

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 states a precondition ('Once a feature built from an idea is live'), an explicit exclusion ('never a thread with a draft or a recorded reply already'), and a mandatory consent flow ('tell the founder the price and wait for a yes'). It does not name a direct alternative sibling to route to when the precondition fails, which keeps it short of a 5.

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