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

Goes well beyond the annotations: 202 async acceptance, multi-minute duration, where the result lands (`url` on the Current Process step), versioning over an existing map, and the full set of 409/403 refusal causes including permission tiers (creator or Lead Builder+). Only gap is that it doesn't discuss whether an in-flight version can be cancelled or what the 202 payload contains, so not quite a 5.

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?

Content is front-loaded with the action, but the description is one dense run-on sentence packing refusals, permissions and sequencing into comma-chained clauses. Nothing is wasted, yet the 409/403 causes would be far easier to act on as a short list.

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?

For a single-parameter async mutation with no output schema, it covers timing (202, minutes), result location (`url`), idempotency-adjacent behavior (writes a new version), failure modes and authorization. An agent has everything needed to call it correctly and set expectations.

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?

Only one parameter and schema coverage is 100%, so the schema fully documents `automation_id`. The description never mentions the parameter or its constraints (e.g. the UUID must belong to a setup the caller owns), so baseline 3 applies — schema carries the load.

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 ('Generate current process map for a Module automation being set up') and anchors it to the concrete UI action it mirrors ('the same as pressing it in the web app'). It also names the sibling that follows it (`generateAutomationProposal`), so an agent can place it in the workflow without opening any schema.

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 (setup step for a Module automation), an explicit precondition ritual ('Confirm with the user before calling: say it writes the map from what setup has collected'), and the exact successor step. Also enumerates when-not-to-call via 409/403 conditions, leaving nothing to inference.

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