Bind a flow's connection

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

With no annotations, the description carries the full behavioral burden and does so: it discloses auto-resolution behavior, that it handles two distinct storage shapes (directly-named connection edited in place vs. a connectionreference row bound for solution flows), that it mutates a live environment and requires confirm: true, and the activation side-effect of activate: true.

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?

Three sentences, front-loaded with the purpose and the enables-activation framing, then edge-case behavior, then the mutation confirmation requirement. No wasted clauses.

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?

For a 12-parameter mutation tool with no annotations and no output schema, the description adequately covers prerequisite (confirm), side effect (activate), and the branching behavior. It omits return/error semantics and success signaling, which are minor given the schema documents defaults and dry-run behavior.

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 the baseline is 3, but the description adds real semantics beyond the schema: it explains the reference/connectionId correlation (which is auto-resolved when singular, chosen otherwise) and the two binding paths that govern which parameters apply. It still doesn't clarify connector-vs-reference selection precedence or defaults in prose.

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?

States a specific verb (bind) and resource (a flow's connection reference), and adds the crucial scope that this is the step that enables a flow to be switched on. An agent can distinguish it from cs_set_flow_state, cs_update_flow, and cs_create_connection without opening any schema.

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?

Gives clear context for when this tool is needed and how its arguments resolve ambiguity ('Picks the reference and the connection for you when there is only one of each, and asks when there is a choice'), plus the activate-in-same-call path. It stops short of naming sibling alternatives explicitly (e.g. when to bind vs. use cs_set_flow_state or cs_update_connection), so not a 5.

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