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

With no annotations, the description carries the full behavioral burden, and it does disclose the return payload in substance (steps, connections, and what stops the flow running) as well as the read/non-mutating framing implied by "Fetch". It stops short of stating auth requirements, rate limits, or error behavior, so it is not exhaustive for an annotation-free tool.

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 with the core action, then progressively adds intent examples, exclusion guidance, and a return summary; no sentence is filler. It is dense and slightly run-on with the quoted intent phrases, which costs a point but keeps the routing information compact.

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 two-parameter read tool with no output schema and no annotations, the description covers what the agent needs: what it returns, which parameter narrows the result, how to obtain the id in the common page context, and which sibling to use for write intents. Nothing essential to calling 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 0%, so the description must compensate, and it does: flowId is explained contextually (already present in <page_context> on a flow page) and nodeId is explained as accepting an id OR a name and returning a single step's data. That resolves the most likely ambiguity, though it doesn't cover formatting or failure modes for an invalid id.

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 ("Fetch one flow by id") and immediately scopes it against siblings by enumerating the user intents it serves: seeing, inspecting, opening, and checking configuration/triggers. An agent can distinguish this from list_flows, search_flows, and get_flow_stats without opening any schema.

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?

Gives explicit when-to-use with natural-language user phrasings ("what does this flow do", "show me the welcome flow"), plus an explicit when-NOT-to-use: it is not a lookup before an edit, and edit requests should go to the write tool instead. It also tells the agent that on a flow page the id is already in <page_context> and can be passed directly.

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