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

Goes well beyond the annotations: it discloses that the created Automation starts in setup and does not run yet, that the 409 refusal leaves state unchanged, and that convert_existing_demo deletes sample cases and Runs with no undo. The destructiveHint annotation is corroborated and made specific rather than merely restated.

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?

Front-loaded with the action, then the refusal semantics, then the required next step — a logical order with no filler sentences. It is dense and longer than typical, but each clause carries operational information.

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?

No output schema exists, yet the description still tells the agent to give the user the `url`, and it covers the post-call state ('starts in setup'), the next tool to call, and the deferred setup phases. Nothing needed to invoke or follow up correctly is missing.

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%, so the schema already explains slug, team_id and convert_existing_demo in detail. The description reinforces the convert_existing_demo consequence and the team-scoping context, but adds little syntax or format detail beyond the structured fields — baseline 3 applies.

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 ('Set up a Duvo Module ... as a new Automation on the team') and grounds it in a concrete UI action, with named examples (AP Invoice Intake & Routing, Freight Audit). It also lists what the call materializes (Agents, code steps, Queues, Policy, dashboards), which distinguishes it from generic siblings like createAutomation or buildClarityAutomation.

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?

Explicit sequencing: call getAutomationReadiness next, and don't raise connections/routing until the approved proposal is being built. It also gives a hard precondition for convert_existing_demo ('ask the user first') and explains the 409 refusal path, so an agent knows both when to use it and when not to.

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