flow_manage_project

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the two surface behaviors but does not disclose side effects of creating a project, whether creation is permanent or reversible, permission requirements, or potential failure modes. For a tool with a mutating action, this is a meaningful gap.

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 a single front-loaded sentence that names both capabilities with no filler or redundancy. Every word contributes to understanding the tool's scope.

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 dual-action tool with no annotations and no output schema, the description is too lean. It does not explain what a 'list' call returns, how naming conflicts are handled on create, or what side effects creation has on the user canvas. The schema covers parameters well, but the surrounding behavior is not fully specified.

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 100%, with 'action' having an enum and default, and 'name' explicitly documented as required when action is 'create.' The description adds no additional parameter semantics, but the schema already carries the necessary meaning.

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 names both distinct actions, 'Lists existing Flow projects' and 'creates a new project,' and identifies the resource and scope ('on the user canvas'). This clearly differentiates it from sibling tools like flow_generate_image, flow_generate_video, flow_connect, and flow_status.

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 through the 'list' and 'create' actions but provides no explicit guidance on when to prefer this tool over siblings or when listing versus creating is appropriate. There are no exclusion criteria or alternative routing, so the guidance is only implicit.

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