Schedule a post

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

Description discloses critical behaviors beyond annotations: the post only fires while the server runs, past-due jobs execute on next startup, and local media files must still exist when the job fires. This context is essential for correct usage.

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 a single paragraph that efficiently conveys purpose, parameter usage, and warnings. It is front-loaded with the main action. A minor improvement could be breaking into shorter sentences, but overall it is concise and structured.

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 all parameters and key behavioral caveats given no output schema. However, it does not mention what the tool returns (e.g., a job ID). This is a minor gap, but the description is otherwise complete for a scheduling tool.

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 baseline is 3. The description adds meaningful context: timezone handling for `at`, duration formats for `in`, optionality of `text` when media provided, and resolution timing for `media`. It enhances understanding 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 clearly states the tool schedules a text/media post for later publishing. It distinguishes from siblings like 'create_thread' (immediate post) and 'cancel_scheduled' (removes a scheduled post).

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 explicitly explains when to use `at` vs `in` with examples, warns that the post only fires while the server is running (with past-due jobs on startup), and advises running as a daemon for long horizons. It also notes that local media paths must exist at firing time.

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