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

The annotations already disclose that this is destructive, non-idempotent, and open-world, while the description adds useful timing context: posts are written immediately but scheduled at their planned dates. It does not explain credit consumption, reversibility, or other side effects beyond what the annotations imply.

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?

Two sentences, front-loaded with the core behavior and followed by the intended use case. There is no wasted wording.

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 description, schema, and annotations together give enough context to call the tool correctly: campaign id, optional count, immediate writing, and planned-date scheduling. It could be stronger by explicitly noting credit or irreversibility implications, but the key behavioral traits are largely covered.

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 100%, and the schema documents id and count. The description adds only the phrase 'next few posts,' which loosely corresponds to count but does not add meaningful semantics beyond the schema.

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 gives a specific verb and resource: writing the next campaign posts immediately rather than waiting for lead time. It distinguishes this behavior from ordinary campaign scheduling, though it does not explicitly name sibling tools such as plan_campaign or start_campaign.

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 provides a clear use case: showing the user what the campaign plan actually produces. However, it does not state when not to use it or name alternative tools for normal campaign execution.

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