create_posts_batch

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

The content itself is unusually rich beyond the annotations: irreversible public posting after scheduled_at passes, partial-batch success with failed items returned by index, and a required confirm flag. However, it labels itself a "DESTRUCTIVE WRITE" while the annotations declare destructiveHint=false, a direct inconsistency that forces the agent to choose between structured metadata and prose; the disclosure is the safer of the two, so this is not a full-severity contradiction, but it is a real mismatch.

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?

Front-loaded with purpose and the destructive warning, then organized under REQUIRED BEFORE CALLING and AFTER CALLING headers. Every sentence carries operational weight; nothing is repeated from the schema.

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?

For a high-blast-radius batch mutation with no output schema, the description covers the safety preconditions, the irreversibility window, the partial-failure return shape, and what the agent should report back including the dashboard link. An agent has enough to call this correctly and safely.

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 the baseline is 3, but the description adds cross-reference meaning the schema cannot express: each array item accepts the same fields as create_post, including thread_posts, platform_settings, instagram_settings, media URLs, and workspace_id. It does not explain the confirm semantics beyond the schema's own const/description, which keeps it from a 5.

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?

Opens with a specific verb, resource, and scope: "Create 1-25 scheduled or immediate social posts in one API request." That immediately separates it from the single-post sibling create_post and from validate_post, and the batching limit is stated up front.

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?

Gives explicit when-to-use sequencing: call whoami first, preview every post with named fields (account/platform, caption, timezone, media, settings, workspace), then obtain explicit confirmation and never infer consent from an earlier plan. It also names the post-call behavior and points at create_post as the per-item field reference.

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