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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the trailing 'Read-only' is largely redundant. The description still adds real behavioral context beyond annotations: the connection-binding scoping behavior and the shape of what comes back (title, schedule, {{variables}}, run stats).

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?

Three short sentences, front-loaded with the core action and the resource definition, then scoping, then the safety note. No filler and nothing out of order.

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-optional-parameter list tool with a full output schema and complete annotations, the description covers action, resource, scoping behavior, returned fields, and safety profile. Nothing an agent needs to invoke it 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 description coverage is 100%, so both enum values and the binding-dependent default are already documented in the schema. The description restates the same scope semantics without adding syntax, format, or edge-case detail, so the baseline of 3 applies.

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 ('List the user's saved workflows') and immediately defines what that resource is with a parenthetical gloss ('prompt-templated browser automations, docs.webrun.ai'). It also enumerates the returned fields, which cleanly separates it from the singular get_workflow sibling.

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?

Explicitly describes the selection rule for the scope parameter: default is the bound environment, and 'all' broadens to every environment. It gives clear context for when each mode applies, but never names an alternative tool (e.g., get_workflow) or states when not to use this one.

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