Create several posts

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

Annotations already declare the write/destructive, non-idempotent, open-world profile, so the description's job is to add behavior beyond that. It does so with the key non-obvious trait: per-item ok/error results and partial success ('successful ones are created even when others fail'). It stops short of stating default scheduling/publish behavior when scheduledAt is omitted.

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?

Three tight sentences: capacity first, item shape second, failure semantics last. Every sentence carries information an agent needs and 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 batch-create tool, the highest-risk misconception is expecting all-or-nothing behavior, and the description pre-empts that clearly. Remaining gaps are default publish-vs-schedule behavior and the unmentioned bulk_posts sibling, both of which matter for correct tool selection.

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?

There is a single top-level 'posts' parameter with no description in the schema, so the description must compensate. It adds the crucial semantic that each item mirrors create_post's fields and reinforces the 25-item cap, but it delegates all item-field meaning to another tool's docs, which the agent may not have loaded.

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?

Names a specific verb and resource with scope: 'Create up to 25 posts in one call', and implicitly positions itself as the batch counterpart of create_post. It does not distinguish itself from the sibling bulk_posts, so an agent cannot fully tell the two apart from this description alone.

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 phrase 'for example a week of scheduled content' implies the intended use case (batching scheduled content), but there is no explicit when-not guidance, no direction on choosing between create_posts, bulk_posts, or repeated create_post calls, and no note about atomicity trade-offs when deciding to batch.

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