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 of behavioral disclosure. It mentions 'advanced automation' and 'optimal timing' but does not explain what these entail (e.g., recurring schedules, auto-hashtags, time optimization). It also does not disclose that this is a write operation with future effects or any other side effects. The description adds little beyond the name and schema.

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 sentence with no filler words. It is front-loaded with the key verb and resource. However, it could be more informative without sacrificing brevity, such as mentioning the automation settings or the scheduling datetime. Still, it is concise and free of redundancy.

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 tool's complexity (nested automation_settings object, 5 parameters) and the absence of both annotations and an output schema, the description should provide more context. It does not clarify what 'advanced automation' includes, what the tool returns, or any prerequisites. This is inadequate for an agent to fully understand the tool's behavior.

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 80%, and all parameters have descriptions in the schema (text, timezone, media_url, schedule_time, automation_settings). The description adds no parameter-specific semantics beyond what the schema already provides, so baseline 3 is appropriate.

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 ('schedule') and resource ('posts'), clearly indicating the tool's core function. The phrase 'advanced automation and optimal timing' adds context, though it is somewhat vague. It distinguishes from siblings like publish_thread, which implies immediate publishing.

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?

No guidance is provided on when to use this tool versus alternatives such as publish_thread or create_post_with_restrictions. There is no mention of prerequisites, exclusions, or scenarios where immediate posting would be more appropriate. The usage context is only implied by the verb 'schedule'.

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