schedule_posts_bulk

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 only states 'schedule multiple posts' and does not disclose potential side effects, validation behavior, error handling, authentication requirements, or what the response looks like. It lacks any detail about whether scheduling is atomic, asynchronous, or reversible.

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 that clearly communicates the core action with no unnecessary detail. It is front-loaded and 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?

The tool has a nested array parameter and no output schema, yet the description provides no information about return values, error scenarios, limits, or prerequisites. It is far too minimal for an agent to use effectively beyond the basic intent.

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 0%, and the description merely says 'multiple posts', which maps to the 'posts' array parameter but does not explain the required fields (account_ids, text) or their meaning. The schema shows the structure but no descriptions, so the agent gets little guidance on what a post object must contain.

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') with clear scope ('multiple at once'). It effectively distinguishes this tool from sibling 'schedule_post' by indicating it is for bulk operations.

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 the tool is for scheduling multiple posts in a single operation, which provides clear context for when to use it. However, it does not explicitly mention alternatives like 'schedule_post' for single posts or state when not to use it.

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