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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: it is a preparatory reading resource whose content includes three complete worked examples, implying a substantial reference payload. It says nothing about response size or format, keeping it at 4.

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?

Two sentences, front-loaded with the imperative 'READ THIS FIRST' so the most actionable instruction leads. The second sentence enumerates the guide's contents tersely with no filler; every clause earns its place.

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 zero-parameter reference tool with no output schema, the description adequately conveys what an agent will receive when it calls it. It could note the output modality (returned documentation text) or roughly how large the content is, but what an agent needs to decide to call it is present.

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 tool takes zero parameters and the schema is empty with 100% coverage, so the baseline of 4 applies. There are no parameters for the description to illuminate, and it correctly does not invent any.

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 precisely what the tool is and returns: a reference covering document shape, the settings-vs-input-ports rule, link format, plugin links, and worked examples. It is unmistakably a flow-authoring documentation resource, distinct in kind from the flow CRUD siblings. It stops short of naming a specific sibling it competes with, hence 4 rather than 5.

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?

'READ THIS FIRST before writing or editing any raw flow orchestration JSON' gives an explicit trigger condition (before authoring/editing raw JSON). It doesn't name the alternative tools (flows_edit_text, flows_scaffold, flows_update) or state when the guide is NOT needed, but the intended usage window is clear.

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