schedule_post

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

With no annotations, the description carries full burden. It only states the equivalence and scheduling, but omits behavioral traits like error handling for past dates, whether the post is modifiable, or if it validates social_accounts connectivity. Lacks depth for a mutation tool.

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?

Single sentence, no waste, front-loaded with purpose. Could be slightly expanded without harming conciseness, but currently efficient.

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?

Despite complex nested schema and no output schema, description is very thin. Doesn't mention media, platform_configurations, or per-account overrides. Lacks completeness for an agent to fully understand what the tool does beyond the shortcut equivalence.

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 already covers all 7 parameters with 100% description. The description adds no extra parameter meaning beyond implying scheduled_at is used. 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?

Clearly states it's a shortcut to schedule a post for a future time and names the equivalent create_post call. Distinguishes from create_post by specifying the default scheduled_at and status='scheduled'. However, it doesn't contrast with other sibling tools like publish_now or create_draft.

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?

Describes itself as a shortcut but gives no when-not-to-use guidance, no prerequisites, and no comparison to alternatives beyond create_post. Agent may not know when to prefer this over create_post with manual scheduled_at.

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