add_connector_action

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

There are no annotations, so the description must disclose behavioral traits, but it only hints at wiring connectionReferences. It does not state that this is a mutation, what changes to the local flow, any side effects, reversibility, or error behavior. For a write operation this is a significant gap.

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 efficient sentence with the main action front-loaded and no filler. However, its brevity prioritizes compactness over operational detail, and the parenthetical could be clearer.

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?

With no annotations, no output schema, no parameter descriptions, and a nested inputs object, the description is not complete enough for safe invocation. An agent cannot tell what inputs are expected, what happens if the connection does not exist, or what the result of the operation is.

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 does not explain connector, operationId, inputs, or connectionName. The phrase 'wies connectionReferences' weakly hints at connectionName's role, but the shape of inputs and the meaning of operationId are left undocumented, so the description does not compensate for the lack of schema descriptions.

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 action ('Add connector action to local flow') with a clear verb and resource, and the parenthetical 'wires connectionReferences' adds useful implementation context. It is clear at a high level but does not explicitly distinguish itself from sibling tools like update_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?

No guidance is given about when this tool should be used instead of alternatives such as update_flow, ensure_connection, or sync_push. The description does not state prerequisites, such as whether the connection/connector must already exist, leaving usage decisions to inference.

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