create_cloudflow_connection

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

Annotations already indicate readOnlyHint=false and destructiveHint=true. The description adds behavioral context: the tool is for creation, requires confirmation, and that it connects an account for automation. It does not detail potential side effects (e.g., costs), but provides useful beyond-annotation guidance.

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 three sentences, concise, and front-loaded with the core purpose. Every sentence adds essential information with no redundancy.

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?

Given the tool's complexity (nested objects, no output schema), the description covers purpose, usage constraints, and confirmation needs. It does not explain return values or error scenarios, but for a create tool with clear sibling differentiation, it is reasonably 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?

Schema coverage is 100%, so baseline is 3. The description adds value by emphasizing the mutual exclusivity of gcpConfig and awsConfig and the need for user confirmation. It does not repeat parameter schemas but adds contextual usage hints.

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 it creates a new CloudFlow cloud provider connection (GCP or AWS). It uses a specific verb ('create') and resource ('CloudFlow connection'), and distinguishes from sibling tools like update_cloudflow_connection and trigger_cloud_flow.

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 explicitly says 'Use this when the user wants to create...' and provides when-not-to-use guidance (do not use for updates or triggering). It also specifies the constraint that exactly one of gcpConfig or awsConfig must be supplied, and advises confirming with the user before executing.

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