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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description still adds real behavioral context the annotations cannot: workspace-scoped catalog contents and the `allowed: false` flag on policy-forbidden model nodes with the instruction to avoid authoring with them. It doesn't cover pagination limits or result shape beyond the summary/detail split, so it sits a notch above the annotation baseline rather than far above it.

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-loads the authoritative-source claim, then mode selection, then the conceptual distinction between ports and settings, then the workspace policy caveat and `flowId` behavior. Every clause carries a decision or a constraint; nothing is filler.

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?

No output schema exists, yet the description covers what comes back (summaries vs full node detail), the `allowed` flag, and the flow-pinned imports shape. Combined with the workspace requirement and the authoring-guide cross-reference, an agent has everything needed to call it correctly in either mode.

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?

With 100% schema description coverage the baseline is 3, and the description clears it by explaining mode semantics: which parameters produce summaries vs single-node detail (inputs/outputs/settings) and what `flowId` actually injects (pinned imports as `imported-<uuid>` nodes). The `workspace` policy note reinforces rather than repeats the schema text.

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 (search / get) plus resource (Workbench node catalog) and its scope: node existence and their actual ports. It positions itself as ground truth and differentiates from siblings by pointing at `workbench_flow_authoring_guide` for authoring semantics.

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 routes between two modes — keyword/category for summaries vs `slug` for full detail — and states the anti-pattern it replaces ('verify against this instead of recalling'). It also names a sibling tool for adjacent concerns and gives the policy rule ('never author with those; pick an allowed model'), so an agent knows both when to call and what to do with the result.

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