save_integration_flow_version

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

With no annotations, the description must disclose behavioral traits. It only says 'save... as a new version' but fails to explain what saving entails—such as whether it creates a new version from scratch, the relationship between current and new version, or any side effects. Essential behaviors are missing.

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 very short (one sentence), making it concise and front-loaded. However, it sacrifices necessary details, and the brevity does not serve the agent's need for clarity.

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 (4 parameters, no annotations, no parameter documentation), the description is incomplete. It does not explain how to use the parameters or what the tool returns, despite the presence of an output schema. The agent lacks sufficient context for correct invocation.

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 0%, and the description provides no explanations for the four parameters (iflow_id, current_version, new_version, artifact_content_base64). The agent cannot infer the meaning or expected values of these parameters from the description.

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 verb 'save' and the resource 'integration flow as a new version', distinguishing it from siblings like create_integration_flow and update_integration_flow. However, it does not explicitly differentiate from other version-related operations.

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?

No guidance is provided on when to use this tool versus alternatives such as update_integration_flow or create_integration_flow. The description lacks context about prerequisites or appropriate scenarios for saving a new version.

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