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

Goes well beyond the annotations (idempotentHint, destructiveHint=false) by disclosing automatic-retry precedence, the seven-day/oldest-first/ten-minutes-apart batching for the no-postId case, the refusal conditions (expired sign-in, disconnected account), review-mode restrictions, and a per-network retry cap of three. This is exactly the operational context an agent needs.

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?

Purpose and the auto-retry caveat are front-loaded, and each subsequent sentence adds distinct operational detail (batching, refusals, rate limit). Density is high but phrasing is convoluted in places (e.g. 'sends a busy network, an unprocessed file and a network's limit again by itself first'), which costs a little readability.

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 mutating tool with no output schema, the description covers the failure semantics, refusal paths, credential restrictions and retry limits an agent needs to call it correctly, and defers nothing important. No output-schema-dependent gaps remain.

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%, so the schema already documents both params; the description still adds value by spelling out the batch semantics of omitting postId (all profile posts with a failed channel in the last seven days, oldest first, spaced ten minutes) and the narrowing behavior of channels. Slightly above the baseline because it adds format/timing meaning not in the schema.

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 (re-send a post) and precisely scopes it to 'the networks that did not take it; where it is already out, nothing changes'. It also distinguishes the two modes (with vs. without postId) and routes the agent to get_post to confirm failure, so it is separable from siblings like cancel_post and update_post.

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?

Explicitly says to use this 'for a channel that still reads failed in get_post', and explains that Mellow Hub already re-sends busy-network, unprocessed-file and rate-limit cases automatically — a clear when-to-use vs. when-not-to. It also names the conditions under which the call is refused.

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