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

Annotations already establish a safe read-only, closed-world profile, but the description adds real behavioral context: the catalog is workspace-scoped, policy-forbidden model nodes are returned with `allowed: false`, and personal tokens without a default workspace must pass `workspace`. These are non-obvious traits an agent could not infer from the schema or annotations.

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?

Front-loaded and dense with no filler: the ground-truth claim comes first, then search/detail modes, then the workspace policy caveat. It is packed tightly and borders on over-compressed, but every sentence conveys distinct 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?

For a read-only, 7-parameter tool with no output schema, the description covers purpose, key parameter roles, workspace policy behavior, and the cross-reference an agent needs. It does not address the paginated result shape or how to interpret `limit`/`offset` behavior, which is a minor residual gap.

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 100%, so the baseline is 3, but the description adds conceptual meaning the schema lacks – that `q` returns summaries while `slug` returns full detail, `flowId` surfaces pinned imports as `imported-<uuid>` nodes, and `inputs` are PORTS fed by links while settings live on the node. Pagination semantics (limit/offset) stay in the schema only.

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 states a specific verb+resource with scope: it is the ground truth for what nodes exist and what their ports are, searchable by keyword/category for summaries or by `slug` for full per-node detail. It also routes away from the sibling `workbench_flow_authoring_guide` for settings-vs-ports guidance, so an agent can distinguish it from related workbench tools.

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?

Explicit when-to-use guidance ('verify against this instead of recalling'), an exclusion ('never author with those [allowed: false] nodes'), and a named cross-reference for the related concern in `workbench_flow_authoring_guide`. This is actionable routing, not implied usage.

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