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

Annotations declare destructiveHint=true, and the description usefully bounds the blast radius: the default touches every failed platform, while `subreddit` leaves siblings — succeeded or failed — untouched. That is exactly the context a destructive tool needs, though it never says what 'retry' actually does (re-publish? duplicate posts?) or whether repeated calls are safe.

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?

Single sentence, front-loaded with the default behavior before the two override parameters, and the parenthetical about siblings earns its place. Slightly run-on, but nothing is redundant filler.

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 tool with no output schema, the description covers all parameter modes and the scope of the mutation, which is enough to invoke it correctly. It is short only on the post-call story — what a retry returns or how failures surface — which is a minor gap given no output schema exists.

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 the schema already states the r/-prefix convention, the entity_id source, and that `account_id` is only meaningful with `subreddit`. The description restates most of this; its only genuine addition is that targeting one subreddit leaves siblings untouched. Baseline 3 fits since the schema carries the semantics.

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 scope: retry failed platforms for a launch, with two explicit operating modes (all failed vs. one reddit destination). An agent can tell what it does, though it never contrasts itself with the sibling retry_launch_content, leaving the retry-platforms vs. retry-content boundary 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 clear conditional guidance: omit `subreddit` to retry every failed platform, pass `subreddit` to target exactly one destination, and add `account_id` only when that destination belongs to a secondary account. No when-not-to-use or alternative-tool guidance is offered, but the selection logic within the tool is unambiguous.

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