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

Annotations already flag destructiveHint=true and idempotentHint=false, so the bar is lower, and the description adds genuinely useful behavior: creation yields an inert draft that sends nothing until activation. That materially softens the safety picture. It does not address permissions, validation failures, or what happens when a step references a non-existent goto id.

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 front-loaded sentences: purpose and draft status first, mechanics second, concrete example third. The example earns its place by making the trigger/step/branch model tangible. Minimal waste, though the step-type list partially duplicates the schema's steps description.

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 nested, 5-parameter creation tool with no output schema, the conceptual model (trigger → steps → branches) is well covered, but the description never says what is returned — notably the new automation id the agent would need to call activate_automation. Error and validation behavior is also unaddressed.

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 only 40%, so compensation matters. The description explains trigger.event firing semantics and lists the step vocabulary, and the worked example anchors 'wait 3600s' and a condition check, but it says nothing about 'from', 'name', 'topic_id', or trigger.filters.

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 uses a specific verb and resource ('Create a triggered text flow') and immediately scopes it as '(as a draft)', plus enumerates the step types the automation can contain. It doesn't name siblings like update_automation or activate_automation directly, though 'until activated' gestures at the latter.

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 establishes clear usage context: automations are built as drafts and do nothing until activated, which implicitly routes the agent to activate_automation afterward. It gives a concrete worked scenario (cart_abandoned → wait → conditional reminder), but no explicit exclusions versus update_automation or create_schedule.

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