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

The description discloses that leads are set to 'waiting' status and processed by the workflow executor. It also implies that this tool can re-trigger leads already entered, unlike add_to_sequence, which is critical behavioral information. This goes well beyond the annotations, which only indicate non-read, non-idempotent behavior.

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?

Every sentence contributes: scope, execution behavior, prerequisite tools, and the key alternative with its crucial safety distinction. The description is dense but not bloated, and the most important operational details are front-loaded.

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 is complete for a non-read tool with only two parameters. It explains prerequisites, side effects, and the key distinction from the chaining mechanism. There is no output schema to document, and the absence of return-value details is acceptable.

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 0% schema description coverage, the description carries the burden of explaining parameters. It clarifies that workflowId identifies the target workflow and leadIds are for specific leads while omitting leadIds triggers all leads. It could explicitly name the parameters and mention that leadIds is optional, but the semantic intent is clear enough for correct invocation.

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 states a clear action ('Trigger workflow execution') and the exact scope ('specific leads or all leads in the workflow's lead list'). It also differentiates from related tools by naming campaignstack_list_workflows and campaignstack_get_lead_list, and by contrasting with the add_to_sequence node for chaining workflows.

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 explicitly tells the agent what this tool is for and when to use alternatives: list workflows to find IDs, get lead list to see leads, and use integration:add_to_sequence for chaining from inside a workflow. The loop-safe contrast clearly defines a boundary where this tool should not be used.

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