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

Annotations already provide idempotentHint and destructiveHint, and the description adds meaningful process context beyond them: that media validation occurs first, the post is re-queued, and publication is automatic via the scheduler. This helps the agent anticipate the asynchronous flow. No contradiction with annotations.

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 waste. The key discriminator (FAILED) leads, and the internal pipeline is conveyed compactly.

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 retry tool with no output schema, the description explains the full lifecycle after invocation. It covers the validation step, the re-queue, and the automatic scheduler publish, which is sufficient for a caller to know what will happen.

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 there is only one parameter (post_id), documented as 'Socializioz post ID.' The description adds nothing beyond the schema, so the baseline of 3 is appropriate since the schema already carries the full burden.

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 (retries) and resource (a FAILED post), with the retry pipeline spelled out (media validation → re-queue → scheduler auto-publish). The FAILED qualifier distinguishes it from sibling publishing tools like invoke_publish_now and invoke_schedule_post, though it doesn't name them 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?

The FAILED condition implies when to use it (only for failed posts), but there are no explicit exclusions or named alternatives. An agent must infer the appropriate selection among publish_now, schedule_post, and reschedule_post rather than being told.

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