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

With no annotations provided, the description carries the full burden. It discloses that flows are generated as background DRAFTs and 'nothing goes live', which is critical behavioral information. It also mentions the ≤10 split constraint. It doesn't cover permissions or error behavior, but the core non-destructive nature is clear. The 'background' hint implies asynchronous operation, which is helpful.

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 with no fluff. The first sentence states purpose and behavior; the second provides usage conditions, alternatives, and invocation guidance. All critical information is front-loaded, and every sentence earns its place.

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 bulk-generation tool with no output schema, the description covers the essential decision points: when to use, what it produces (drafts, ≤10), and how to invoke it. It lacks details on return format or failure modes, but these are not critical for selection and invocation. The description is sufficiently complete for an agent to act on it correctly.

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 both parameters. The description adds value by explaining the 'description' parameter content (user's own words, keywords, copy, links preserved) and noting accountId defaults to the selected account. This goes beyond the schema's basic 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 clearly states the tool's purpose: bulk-building automations from a whole-setup description, splitting into up to 10 drafts. It explicitly contrasts with generate_flow for single automations, distinguishing it from siblings. The verb 'bulk-build' is specific and the resource (automations) is clear.

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 explicitly states when to use: ONLY for multiple automations described at once, and singles out generate_flow for a single automation. It also instructs to call this directly as the first action without whoami/context lookup, providing concrete guidance on invocation sequence.

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