schedule_post

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

With no annotations provided, the description carries the full burden. It discloses key behaviors: creating, scheduling, saving as draft, and publishing immediately. It does not mention side effects like irreversibility or auth requirements, but the core behavioral distinctions are clearly described.

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?

The description is three concise sentences with no redundancy. Each sentence adds distinct information: main action, draft behavior, and publish_now behavior. It is well-structured and front-loaded with the primary purpose.

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?

The description covers the primary modes and the main parameters, but it omits optional parameters like labels and media_urls, and does not mention the return value or post-creation behavior. Since there is no output schema, a brief note on what is returned would have improved completeness.

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?

The description adds meaning beyond the schema by explaining that omitting schedule_at saves as draft and that publish_now=true overrides scheduling. It also names the required parameters (body text, account_ids). It does not cover labels or media_urls, but those are optional and less critical.

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 clearly states the tool's purpose with a specific verb and resource: 'Create and schedule a post.' It distinguishes from sibling tools like edit_post, cancel_post, and list_posts by focusing on creation and scheduling. The mention of scheduling, draft, and immediate publishing further clarifies the scope.

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 description provides clear context on how to use the tool: pass body text, account ids, and an ISO 8601 schedule_at; omit schedule_at for draft; use publish_now=true for immediate publishing. However, it does not explicitly mention when to use this tool instead of alternatives like edit_post or cancel_post, so it lacks full exclusion guidance.

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