schedule_post

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

There are no annotations, so the description carries the full burden. It conveys that this is a scheduling/write operation but does not disclose return values, failure behavior, confirmation of the scheduled post, permissions, or other side effects. The prerequisite note is helpful but insufficient for full transparency.

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 concise sentences with no filler. The purpose is front-loaded, followed by the key prerequisite and multi-account behavior. Every sentence contributes useful information.

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 schema plus prerequisite guidance cover the main invocation steps, and the description explains the multi-account pattern. However, for a mutating scheduling tool with no output schema or annotations, it would benefit from saying what a successful call returns or how scheduling is confirmed.

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 description coverage is 100%, so the schema already documents all four parameters. The description adds value by clarifying that socialAccountId must come from list_connected_accounts and that each call targets one account, but it adds no extra meaning for content, mediaUrl, or scheduledFor beyond the schema.

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 uses a specific verb and resource: 'Schedule a post to one connected social account.' It clearly states the scope (one account per call) and is easily distinguished from sibling tools like list_scheduled_posts, delete_scheduled_post, and get_analytics_summary.

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?

It gives explicit guidance to call list_connected_accounts first to obtain a valid socialAccountId, and explains how to handle multiple platforms by calling this tool once per account. It does not explicitly contrast with sibling tools or state when not to use it, but the context is clear.

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