schedule_post

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the basic action of creating a scheduled post but does not mention side effects, required permissions, return values, rate limits, or what happens if the scheduled time is in the past.

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, short sentence with no wasted words. However, it is borderline under-specified for a tool with 12 parameters and no output schema, sacrificing completeness for brevity.

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?

Given the complexity (12 parameters, nested objects, no output schema), the description is insufficient. It does not explain what the tool returns (e.g., post ID), how required and optional fields interact, or any post-condition behavior. The description fails to compensate for missing annotations and output schema.

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 no additional context beyond the schema's parameter descriptions. For nested objects like 'repost' and 'youtube', the schema provides descriptions but the tool description does not clarify usage scenarios or relationships.

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 action ('Create a Postoria post') and the specific constraint ('scheduled for a specific UTC date-time'). It distinguishes this tool from siblings like 'publish_post_now' (immediate) and 'add_post_to_queue' (queued) by specifying scheduling.

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 implies this tool is for scheduling posts but does not explicitly state when to use it versus alternatives like 'publish_post_now' or 'add_post_to_queue'. No guidance on prerequisites or exclusions is provided.

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