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

Annotations supply only openWorldHint=true, so the description carries most of the behavioral burden — and it delivers: it discloses the contact-creation side effect, that the workflow must be ACTIVE, and that the operation waits before reading the log. It does not state whether a failed run is retried or what auth is required, but the key mutation and state requirements are covered.

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?

Four tight sentences that lead with the purpose in caps, then behavior, then usage, then prerequisite. Nothing is filler; the prerequisite is deliberately placed last as the immediate next action.

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?

With an output schema present it needlessly but harmlessly narrates the return shape, and it covers prerequisite, side effect, and usage intent. Minor gaps remain around cleanup of the persisted test contact and failure semantics, but nothing blocking for correct invocation.

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 100%, with the email parameter carrying especially rich notes on contact creation and test-artifact tagging, so the schema does the heavy lifting. The description corroborates the create-if-missing behavior and references the update_workflow call, but adds no syntax or format detail beyond what the schema already provides — baseline 3 is appropriate.

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 ('END-TO-END TEST for an automation'), then enumerates the concrete behavior: enrolls a contact, waits, returns a per-step run log. It is clearly distinguishable from the similarly-named sibling volanea_test_webhook_delivery, which targets webhooks rather than 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?

Gives explicit when-to-use ('prove a workflow actually works before telling the user it is done') and a hard prerequisite with the exact call to satisfy it ('Activate the workflow first with volanea_update_workflow { status: active }'). It stops short of naming exclusions or pointing at the volanea_cleanup_test_data sibling for post-test teardown, which the test-artifact side effect would suggest.

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