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

Annotations already disclose the non-read-only, non-idempotent, non-destructive profile, so the bar is lower. The description adds real behavioral value beyond that: saving an edit spawns a new automation rather than mutating the existing one, and non-brief automations open read-only. It stops short of stating auth/permission requirements or what the builder returns.

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?

The purpose is front-loaded, which helps, but the remainder is a single dense run-on sentence with nested parentheticals ('its draft, or once Generate published it its live version (saving an edit of it makes a new automation)') that is hard to parse on first read.

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?

There is no output schema, so return values need not be described, and annotations cover the safety profile. The description covers the key edit-vs-read-only nuance but leaves workflow_id unexplained and the opening/closing UI flow ambiguous, which is a gap for a 4-parameter tool.

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 75%, so the schema documents board_id, read_only, and version_id in detail; only workflow_id is undocumented there. The description's 'another automation opens read-only' and the draft-vs-live explanation give some meaning to workflow_id/version_id selection, but it does not compensate for the untagged workflow_id or add format details. 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: 'Open the brief's automation in the builder,' and goes on to distinguish the draft vs. the published/live version. However, it never names or contrasts a sibling like mcp_recipe_list, mcp_recipe_copy, or mcp_recipe_save_draft, so the agent must infer why it would open rather than list or copy.

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?

Usage is implied: opening a brief's automation puts you in an editable builder ('saving an edit of it makes a new automation'), while 'another automation opens read-only.' There is no explicit when-to-use/when-not guidance or pointer to the alternative tools for listing, copying, or saving drafts.

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