create_flow_action

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

Annotations indicate readOnlyHint=false (write operation) and openWorldHint=true (potential external effects). The description states 'Create' consistent with write, but does not elaborate on side effects, required permissions, or the scope of the action. The '[Scripting]' tag hints at code execution but lacks detail on behavior beyond annotations.

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 short sentence with a tag, front-loaded and free of superfluous words. Every element serves a purpose, making it highly concise and efficient for an AI agent to parse.

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?

Despite having 5 parameters, 1 required, and no output schema, the description does not explain the return value, success behavior, or provide guidance on the optional parameters. The open world hint suggests external effects, but the description fails to address this, leaving significant gaps for an agent.

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 coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond the schema; the '[Scripting]' tag relates to the 'script' parameter but does not explain its semantics or requirements. The parameter descriptions in the schema are already clear.

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: 'Create a custom Flow Designer action.' The verb 'Create' and the specific resource 'Flow Designer action' distinguish it from sibling tools like create_flow (creates a flow) and create_subflow (creates a subflow). The '[Scripting]' tag further clarifies the scripting component.

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 for creating a Flow Designer action but does not provide explicit guidance on when to use this tool versus alternatives like create_script_include or create_flow. No 'when not to use' or alternative tool names are mentioned, leaving the agent to infer context from the tool name and tag.

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