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

Annotations already disclose readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the agent knows this is an outbound mutating action. The description usefully adds that content and targets are preserved, but says nothing about what happens if the post is not in a failed state, whether retries are rate-limited, or what errors to expect.

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 sentence with no filler; every clause earns its place by stating the action and the scope it preserves.

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, outbound retry tool with no output schema, the definition covers intent and preservation scope but omits preconditions (must the post be failed?), failure behavior, and result semantics. The annotations and the idempotencyKey description cover part of the gap, leaving it adequate rather than complete.

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%: idempotencyKey carries a rich, self-sufficient description, while postId is undocumented but self-evident from context. The description itself adds no parameter-level meaning beyond implying the post is identified by content/targets, so the schema does the heavy lifting.

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 ('send a failed post to the network again') and adds a scope qualifier ('keeping its content and targets') that helps distinguish it from a recycle/recreate flow. It is clear on its own, though it does not explicitly name siblings like recycle_post or create_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?

Usage is implied by the name and description (use when a post has failed), but there is no explicit when-to-use guidance, no exclusions, and no named alternative such as recycle_post for the case where you want to alter content rather than resend.

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