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

Beyond the annotations, the description discloses that the send is immediate rather than scheduled, and that the tool performs a pre-flight check that reports what still needs fixing if the retry would fail identically. That is meaningful behavioral context for a non-idempotent write (idempotentHint=false), where each call is a fresh send. It stops short of stating quota, rate limits, or what a success response looks like.

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?

Two short sentences with no filler: the action and its immediacy come first, and the failure-reporting behavior follows. Nothing is redundant with the title or with structured fields.

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, non-idempotent mutation with no output schema, the description covers the trigger condition, the timing of the send, and the error-reporting behavior. The main remaining gap is confirmation of what happens on success and whether repeated calls create duplicate sends.

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 the single parameter already documents its provenance from list_scheduled_posts, so the schema carries the load. The description adds nothing about the post_id beyond what the schema says, which meets the baseline for full coverage.

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 states a specific verb and resource ('Sends a post that failed or was skipped again, right away'), which is far more informative than the title alone. It does not, however, distinguish itself from the similar sibling reschedule_post, so an agent must infer the boundary between retrying and rescheduling.

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 condition 'a post that failed or was skipped', which tells the agent the triggering state. There is no explicit exclusion or comparison against reschedule_post, which handles the adjacent task of moving a post to a different time.

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