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

Far exceeds the annotations: it discloses that the call is asynchronous (202 returned immediately, proposal takes minutes), where the result surfaces (`url` on the Automation Proposal step), permission requirements, refusal codes, and an explicit instruction to confirm with the user first because approving the map is what triggers the write. This is consistent with readOnlyHint=false and destructiveHint=false.

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 and the UI analogue, then prerequisites, errors, permissions, and next step in a logical order. It is dense and slightly run-on in places, but nearly every 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, and the description compensates fully by describing the return (202 immediately) and where the eventual result appears. With two parameters, async behavior, and a permission gate, nothing an agent needs to call this 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 coverage is 100%, so the baseline is 3, but the description adds real constraint semantics: the snapshot must be the team's live map, and omitting it approves whichever map is live. That is meaning beyond the schema's UUID pattern and 'leave out to approve whichever map is live' note.

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 (approve the current process map, start writing the automation proposal) and anchors it to a known UI action ("Approve and continue"). It also explains what the output artifact is (what Duvo automates, what stays with the team, where handover happens), so it is unmistakable against siblings like generateAutomationProcessMap and approveAutomationProposal.

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 prerequisites (must call generateAutomationProcessMap first, must have no existing proposal), explicit exclusions and refusal conditions (409 if the map isn't live, a proposal exists, Policy questions are open, or Duvo is already writing; 403 unless creator or Lead Builder), and names the next step approveAutomationProposal.

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