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

Annotations only declare non-readonly/non-destructive; the description goes far beyond by enumerating the concrete effects (builder header, list_flows, open_in_builder, Deerlake catalog, updatedAt bump) and the deployment consequences (hosted web app retained, next deploy_flow publishes next version). This is exactly the mutation context an agent needs.

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 scope, then the deployment behavior, then the exclusion. Every sentence carries distinct, non-redundant information with no 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?

With no output schema and only weak annotation coverage, the description fully covers effects and side effects, so an agent understands the outcome. The remaining gap is parameter-level guidance (flowId, agent) for a tool with three undocumented parameters.

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 carry parameter meaning, but it never names flowId or the agent parameter and only obliquely implies that title is the new name. The 120-char limit and required/optional status are left entirely to the schema.

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 ('Rename a build (flow)') plus the authoritative scope ('across the platform in one call'), which separates it from the many other flow_* tools. An agent can identify this as the dedicated rename operation without opening the 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?

Explicitly carves out what this tool does NOT do and names the alternative ('Does NOT edit the app source: rename a hardcoded old name yourself with write_flow_files'). It also tells the agent when the rename is safe for a deployed build (hostname and version history unchanged).

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