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

Annotations already indicate this is not read-only, and the description adds the useful behavioral detail that the forked template can be run with run_flow. However, it does not disclose potential side effects, permissions needed, or whether the fork is independent of the original, which would be valuable for a mutation operation.

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?

The description is two sentences, front-loaded with the core action, and contains no redundant wording. Every word contributes to understanding the tool's function and typical next step.

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 simple one-parameter tool, the description provides enough context to understand the operation and its relationship to run_flow. However, it does not clarify how this tool differs from the similarly named fork_community_flow, which would make the context more complete.

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 input schema fully describes the single parameter (template_id with context from list_templates). The tool description does not add extra parameter meaning beyond the schema, so the baseline of 3 is appropriate.

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 clearly states the action ('Fork (copy)') and the resource ('a flow template into your workspace'), which is specific and understandable. It hints at a distinct use case from siblings like fork_community_flow, but does not explicitly name the alternative or contrast them.

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?

The description implies usage (when you want to copy a template to your workspace) and provides a follow-up action ('you can run it with run_flow'), which guides the agent. However, it does not explicitly state when to use this tool over similar sibling tools like fork_community_flow or duplicate_flow, leaving some ambiguity.

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