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

Discloses non-obvious behavior the annotations cannot convey: stored times are jittered by up to half the variance window, the pencil is cleared when a penciled time is consumed, drafts never post, and the response reports when jitter occurred. These are exactly the side effects an agent needs before committing a schedule.

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?

Purpose is front-loaded in the first sentence and the rest is a dense run of edge-case rules with little waste. The pencil/penciled-draft idea is restated across three sentences, slightly more repetition than necessary, but nothing is padding.

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?

No output schema exists, and the description covers the important return signal (the reply reports jitter) plus the draft-scheduling path and cross-tool prerequisite (add media via update_draft for Instagram). The only missing piece is any note on what happens on partial platform failure, which is a minor gap for an open-world scheduling call.

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 the baseline is 3, and the description earns a step above it by explaining the targeting rule for platform_account_ids (falls back to the first connected account) and the practical meaning of variance_minutes as an override. It adds real interpretive value rather than restating field text.

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?

Opens with a specific verb and resource: scheduling a post for a date/time across named platforms. It is distinguishable from draft-only tools and from queue-based ones by the explicit 'scheduled_at' semantics, but it never names the adjacent siblings (queue_post, publish_post, draft_post), so the agent must infer the boundary.

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 concrete conditional guidance: use platform_account_ids when multiple accounts exist for a platform, pass variance_minutes: 0 when the user means an exact time, and omit scheduled_at only for penciled drafts. It lacks any explicit statement of when to prefer this over queue_post or publish_post, which is the main gap.

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