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

Annotations already flag this as a destructive, non-read-only, open-world operation, and the description adds important behavior beyond that: each post is validated for subscription, quota, connection health, and caption limits. It also discloses partial-failure semantics, notable for a batch mutation: one failure does not stop the rest. That is exactly the kind of operational context an agent needs before invoking a destructive batch 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?

The description is front-loaded with the core action and its batch nature, then moves through input modes, validation behavior, failure isolation, and return shape. Every sentence contributes operational information; there is no filler.

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 destructive batch mutation with no output schema, the description covers the essential gaps: input mode selection, per-post validation, partial failure behavior, and the shape of results (per-post). Combined with annotations and schema descriptions, an agent has enough to call this correctly and interpret outcomes.

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 schema already documents each parameter well. The description adds relational meaning by clarifying the either/or usage between video_post_ids and video_upload_id, and by noting that platforms applies only with video_upload_id. That goes beyond individual field descriptions.

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 states a specific verb and resource: publishing multiple draft or scheduled posts immediately in one batch call. It explicitly distinguishes itself from the singular sibling publish_now by calling itself the batched equivalent. An agent can tell exactly what this does without opening the schema.

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?

It clearly says to use this when publishing more than one post and names publish_now as the per-post equivalent, which gives the agent a usable alternative. It does not explicitly state the inverse rule, such as 'use publish_now for a single post', so it stops just short of fully explicit when/when-not guidance.

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