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

Annotations already flag destructiveHint=true and idempotentHint=true, and the description adds real value on top: it clarifies that "dismissed" hides rather than deletes, that changes are reversible via "restored", that restoration has a time window, and that the call spends no credits. Missing only edge behavior, such as what happens when setting "done" on an already-done thread.

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?

A single front-loaded paragraph: the core action comes first, then per-status effects, then the restoration constraint and cost note. Semicolon-separated status definitions keep it tight, though the restoration clause is nested enough to require a second read.

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 three-parameter mutation with no output schema, the definition covers the action, each status outcome, reversibility, and cost. The only residual gap is response shape and behavior on redundant status sets, neither of which is likely to block a correct call.

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 100% and each parameter already carries a description, so the schema does the heavy lifting for projectId and opportunityId. The description does add meaningful semantics for the status enum values beyond the schema's one-line "The new status of the thread", which lifts it above the baseline without being exhaustive.

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 ("Changes the status of one Reddit thread") and anchors it to the visible UI ("the same as the buttons on the Reddit Opportunities page"). The three enum values are enumerated, so an agent can immediately distinguish this mutation from read-side siblings like list_reddit_threads.

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?

Explains what each status means in workflow terms (done = handled, leaves open list; dismissed = unwanted, hidden; restored = back on the open list) plus a concrete precondition for restoration tied to maxAgeHours from get_reddit_settings. It stops short of saying when to prefer this tool over generate_reddit_reply-style follow-ups, but for a status-setter the choice context is effectively complete.

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