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

Annotations already declare this a read-only, closed-world, non-destructive operation, so the safety profile is covered. Beyond that, the description adds real behavioral context: which launch methods exist and the important constraint that ERP events are unavailable until a connector event adapter is installed. That prerequisite is not derivable from any structured field.

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 with the core purpose front-loaded and no filler. The closing 'Use before asking one launch question' is slightly compressed to the point of ambiguity, which is the only real deduction.

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?

This is a simple single-parameter read tool with no output schema, and the description effectively previews the return values by naming the supported launch methods. The unstated workflowId semantics and the absence of an explicit sibling comparison are the remaining gaps, but they are modest for a tool this small.

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?

There is one required parameter with 0% schema description coverage, so the description carries the full burden of explaining it. The only hint is the phrase 'a checked workflow', which vaguely gestures at a workflow context but never names workflowId, its format, or what makes a workflow eligible. The gap is minor in absolute terms but entirely unmitigated.

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: it shows the launch methods available for a checked workflow. The sentence also enumerates the option kinds (manual, schedule, API webhook), so an agent knows what comes back. It does not explicitly distinguish itself from the similarly-named trigger_list or trigger_set siblings.

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 phrase 'Use before asking one launch question' gives a genuine sequencing cue, implying it should be called before prompting a user to pick a trigger. However, it names no alternative tool and gives no condition for choosing trigger_list or trigger_set instead, leaving the routing to inference.

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