export_cloudflow_flow

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

Even with readOnlyHint=true and destructiveHint=false already present, the description adds substantial behavioral context: transitive subflow inclusion, tenant-neutral/credential-free output, rebinding of tenant-scoped references as named requirements, unsupported policy/Slack references, and explicit exclusions (credentials, tenant IDs, schedules, execution state). This goes far 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 opening 'Manage CloudFlow.' is generic filler, but the remaining three sentences are information-dense and logically organized: what is serialized, how tenant references are handled, and what is excluded. The length is justified by the tool's complexity.

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?

The description is largely complete for a read-only export tool given no output schema: it specifies output type, portability constraints, and limitations. The main gap is the undocumented includeVariableValues parameter, and the description does not state how the bundle is returned or what happens on missing flows, but these are secondary.

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 only 33%, and the description does not explain includeVariableValues or clarify the exact meaning/format of flowId. It provides only an indirect hint that 'flow' refers to flowId. The description does not compensate for the undocumented parameters, leaving a meaningful gap for agents.

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 a specific operation (serializes a CloudFlow flow plus referenced subflows) and a concrete output (a tenant-neutral, credential-free JSON bundle). It distinguishes the tool from its import sibling by explicitly mentioning the import operation as the counterpart, and from list/management tools by focusing on export/transfer behavior.

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 makes the purpose clear and references the import operation, which implies a migration/backup use case, but it never explicitly states when to use this tool instead of alternatives such as list_cloudflows, build_cloud_flow, or export_cloud_diagram_json. No exclusions or when-not-to-use guidance is provided.

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