Retry post

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered. The description adds that only failed schedules are affected (successful ones untouched), but says nothing about what happens to already-succeeded deliveries, rate limits, or the result of the retry.

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 zero filler; the distinguishing qualifier 'failed' appears early.

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 one-parameter mutation with no output schema, the description leaves open whether *all* failed schedules are retried or only the most recent, and what the caller gets back (counts, errors). Adequate but with clear 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?

Schema description coverage is 0% — postId is a bare string with no format hint. The description only implies 'a post' via the possessive, giving no guidance on whether this is the internal post ID or a platform-native one, which matters given many sibling tools also take postId.

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-queue a post's *failed* schedules. The qualifier 'failed' separates it from reschedule_post and retry_comment/retry_post_csv_import, though it never names those siblings explicitly.

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?

Implies the trigger condition (schedules that already failed) but gives no explicit when-to-use vs. reschedule_post or update_post, and no prerequisites such as post state or account connectivity.

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