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

Discloses the non-error fallback to the most-recently-updated workflow when no browser session exists and notes the _fallback/_warning flag. This goes beyond the readOnly annotation and gives agents accurate behavioral expectations.

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 organized into clear segments: primary purpose, fallback warning, alternative tools, and parameter usage. It is slightly verbose but every sentence adds useful 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?

Given the simple optional parameter and no output schema, the description provides enough context: what is returned, fallback behavior, and how to filter nodes. No critical operational details are 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?

The schema provides no description for node_ids, but the tool description explains that it fetches only specific nodes when used. This compensates for the missing schema coverage, though it could explicitly state that omitting it returns all nodes.

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?

Clearly states it retrieves the workflow currently open in the user's browser, including nodes, edges, and selected node. It distinguishes itself from get_workflow and list_workflows by explicitly naming those alternatives.

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?

Provides explicit guidance on when to use this tool versus alternatives: use get_workflow for a specific workflow and list_workflows to choose. Also explains the fallback behavior when no browser session is active.

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