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

Annotations already convey the non-read-only and destructive nature, and the description adds a meaningful behavioral nuance: it acts on all failed posts in a single operation. However, it does not disclose potential side effects such as re-publishing content, creating duplicate activities, or whether the retry is immediate and irreversible.

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?

The description is a concise single sentence and is front-loaded with the key action. It loses one point because it mostly restates the title with only 'at once' adding new information, making it slightly redundant rather than truly additive.

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?

Given the output schema exists and annotations cover the destructive profile, the description is minimally adequate. Still, for a zero-parameter bulk action, an agent would benefit from more context about the scope of 'all failed posts' and what a retry entails, so the description leaves meaningful gaps.

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?

The tool has no parameters and the input schema already reflects that fully, so there is no gap to compensate for. Baseline 4 is appropriate since the description is not required to explain any parameters.

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?

The description clearly states the action (retry) and resource (all failed posts), and 'all ... at once' semantically distinguishes it from the single-action sibling posts_retry. However, it does not explicitly name or contrast itself with that sibling, so the differentiation is implied rather than explicit.

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?

The description provides no guidance on when to use this tool versus alternatives like posts_retry or posts_list_failed. The intended context is only implied by the wording 'all failed posts,' and no exclusions or preconditions are mentioned.

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