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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description's 'Free, read-only' is consistent with them. It goes beyond the annotations by explaining what each suggestion contains (engagement counts, draft reply in the user's voice) and defining the `kind` categories (busy/early/regular) with their practical implications. It stops short of covering volume or pagination behavior, so a 4 rather than 5.

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?

Front-loads the core identity ('the user's growth assistant: posts... that still wait for a reply') before secondary detail. The parenthetical explanations of busy vs. early add real value but make the middle dense; each sentence still 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?

No output schema exists, so the description carries the burden of describing returns — and it does, listing the fields (author, likes, comments, kind, post, link, draft) plus the engagement object shape. Only the number of suggestions returned and any pagination limits are left unstated, a minor gap for this kind of daily-digest 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?

Zero input parameters, so there is nothing to disambiguate and the baseline is 4. The only parameter-like term mentioned, `mix`, belongs to the sibling setup_growth_assistant and is correctly attributed there rather than misrepresented as an input here.

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+resource with precise scope: posts from the last 3 days on the user's topics that still lack a reply, each bundled with a draft reply and assistant settings. An agent can distinguish it from siblings like get_posts, edit_reply, or regenerate_replies without opening a schema.

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?

Names the alternative explicitly and the conditions that select it: if the user wants more busy threads or more early posts, use setup_growth_assistant with `mix`; if no assistants exist, offer setup_growth_assistant. It also states the follow-on action (help edit the draft; the user posts from their own account), so the agent knows what happens next.

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