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

With no annotations, the description carries the behavioral disclosure burden and does well: it states that the graph is untouched, that a mid-publish flow is rejected, and that flowName performs no id lookup. It does not discuss permissions or return behavior, but the disclosed constraints are substantive and useful.

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 compact sentences with no filler. The core purpose, the key parameter distinction, and the most important exclusions are all front-loaded without repeating schema 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?

The description provides good context for a metadata-only update tool, but it is not fully complete: flowId is present in the schema yet unaddressed, and there is no guidance about required parameter combinations or what the tool returns. Still, the core behavioral constraints are clearly stated.

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. It clearly explains flowName as the current name and name as the new name, and even notes that flowName requires no id lookup. However, the flowId parameter is left unexplained and the description parameter is only implied by the example, leaving valid parameter combinations unclear.

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 action and resource: 'Update a flow's identity fields', and reinforces it with natural-language examples ('rename this flow to X', 'change the description'). It also distinguishes itself from graph manipulation via 'Does NOT modify the graph', separating it from sibling tools like update_node and add_node.

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?

Clear context is provided: this tool is for identity/metadata updates, not canvas/graph changes. It gives useful selection guidance like 'does NOT modify the graph' and 'flowName says WHICH flow', though it does not explicitly name sibling alternatives such as bulk_update_flows or explain when flowId should be used instead.

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