Create Multiple Blog Posts (Batch)

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

Annotations already indicate mutable (readOnlyHint=false), non-destructive (destructiveHint=false), and potential side effects (openWorldHint=true). The description adds critical behavioral details: starts workflows (async), returns workflow_ids, max 25, and polling mechanism, exceeding annotation coverage.

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 action and constraints, every word earns its place. No redundancy or fluff.

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?

No output schema exists; description compensates by mentioning return of workflow_id per item and polling follow-up. Missing details on error handling, async behavior, or scheduling specifics, but adequate for a batch initiation tool.

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?

With 100% schema description coverage, baseline is 3. The description adds value by stating returns one workflow_id per item, which is not in schema, and implies the batch nature. This pushes it above baseline.

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 clearly states the tool starts up to 25 blog-creation workflows on a single website, returns a workflow_id per item, and directs to polling endpoints. It effectively distinguishes from siblings like create_blog (single) and batch_create_pages (different resource).

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 description implies use for batch creation and suggests polling for status. It indirectly indicates alternative single creation via create_blog sibling, but lacks explicit 'use when multiple blogs are needed' or 'avoid for single blog'. Still clear enough.

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