Create a Buffer post

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

Annotations cover the safety profile (openWorld, non-idempotent, non-destructive), and the description adds real behavior: per-channel fan-out, pre-flight platform validation, and Cloudinary-backed media upload. It stops short of explaining failure behavior or rate limits, so it is strong but not exhaustive.

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 short sentences, zero filler, with the fan-out behavior and validation/dryRun workflow front-loaded. Every sentence conveys a distinct operational fact.

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 an 8-parameter mutation tool with nested metadata and no output schema, the description leaves notable gaps: mode option semantics and the confirm-gate are only in the schema. It covers the headline behavior but an agent still needs the schema for the write contract.

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 63%, and the description mainly restates the media parameter while adding only the Cloudinary upload detail; the mode enum values, dueAt requirement, metadata shape and channelIds default get nothing beyond the schema. Baseline 3 fits when the schema carries most of the load.

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?

States a specific verb and resource and adds the crucial fan-out scope: 'Create one post per channel.' An agent immediately knows this differs from buffer_update_post or buffer_create_idea.

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 gives one clear usage path (dryRun to preview, platform validation runs first) but never states when to reach for this versus buffer_update_post or when not to use it. Usage is implied rather than explicitly scoped.

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