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

Annotations indicate idempotent, non-destructive, and readOnlyHint false. The description adds the environmental requirement of a NoClick tab, which is useful context. It does not contradict annotations and provides enough transparency for the action's side effect (opening a browser tab).

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 description is a single, concise sentence with no redundant phrases. It efficiently conveys the tool's purpose and the key prerequisite.

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 simple action, the description covers the main purpose and a prerequisite. However, it does not mention potential error conditions (e.g., workflow not found, tab missing) or any return value, though an output schema exists, which mitigates the need for return-value explanation.

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?

The only parameter `workflow_id` has no description in the schema (0% coverage) and the tool description does not elaborate on its format, source, or meaning. The parameter name is somewhat self-explanatory, but the description fails to compensate for the missing schema details.

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?

The description clearly states the action ('Open'), the resource ('workflow'), and the context ('in the user's browser'), distinguishing it from sibling tools like run_workflow or get_workflow. The requirement of a NoClick tab adds specific context.

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?

The description provides a prerequisite (NoClick tab open) but does not explicitly state when to use this tool versus alternatives. It implies usage for displaying a workflow in the browser, but lacks direct comparison or condition-based guidance.

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