update_cloudflow_connection

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

Annotations indicate destructiveHint=true, and the description confirms mutability by listing modifications. It adds the behavioral detail 'ask the user to confirm the changes before executing,' which aligns with the destructive nature. No contradictions with 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?

Two sentences, front-loaded with purpose, and each sentence adds value without redundancy. Highly efficient and well-structured.

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 7 parameters (1 required), no output schema, and sufficient annotations, the description covers what the tool does, constraints, and usage guidance. It also includes a recommendation to confirm, making it complete for the 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% with descriptions for each parameter. The description adds value by summarizing constraints ('All fields except connectionId are optional; at most one of gcpConfig or awsConfig') beyond the schema, though the schema already provides detailed explanations.

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 'update an existing CloudFlow cloud provider connection' and lists specific updatable fields (rename, description, enable/disable, GCP/AWS config, collaborators). It explicitly distinguishes from create_cloudflow_connection and trigger_cloud_flow, making the purpose unambiguous.

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 tells when to use (update existing connection) and when not to use (not for create or trigger). Also instructs to ask user for confirmation before executing, providing clear usage context.

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