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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true. The description adds the genuine extra context of an approval gate and the mechanism to bypass it, which is not encoded in the annotations. It stops short of saying what the destructive/open-world effect actually is (e.g., external publication).

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 sentences, zero filler, with the core action stated first and the conditional approval rule immediately after. Nothing to trim.

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 4-param mutation with no output schema and full annotation coverage, the description supplies the one thing an agent would otherwise miss: the approval gate and its bypass. Failure behavior and timezone/UTC interactions remain unaddressed, but those are minor here.

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%, so post_id, schedule_at, timezone and override_approval are all already documented. The description's note on override_approval largely restates the schema's own wording, adding no syntax or format detail beyond it — baseline 3.

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?

Clear specific verb+resource: 'Schedules a post.' The description also names the approval prerequisite, which helps separate it from related lifecycle siblings, though it never distinguishes itself from invoke_reschedule_post or invoke_publish_now, which sit adjacent in the tool list.

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?

Gives a concrete conditional rule: pending review requires approve_post, or override_approval=true only when the user explicitly asks to bypass review. That is real when-to-use guidance, but there is no guidance on choosing this tool over reschedule_post or publish_now.

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