Integrations: enable

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

Annotations already declare this is a non-read-only, non-destructive, closed-world operation, so the safety profile is covered. The description adds nothing on top: it does not say whether enabling is idempotent, what state change occurs, or what happens to a previously disabled connection.

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 two-word phrasing is maximally concise and front-loaded, but at this length it is under-specified rather than efficient — it omits context an agent needs for a mutation call.

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 state-changing tool with no output schema, the description should at least say what enabling affects and how it relates to disable/connect. None of that is present, leaving the definition inadequate for correct invocation beyond the bare schema.

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?

With a single parameter at 100% schema description coverage, the schema already documents connection_id, so the baseline is 3. The description contributes no additional meaning, such as where the connection_id comes from (e.g., integrations_connections_list) or its format.

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?

"Enable a connection" gives a clear verb and an object, so the basic action is identifiable. However, it never clarifies that "connection" means an integration connection, nor does it distinguish itself from siblings like integrations_connect, integrations_disconnect, or integrations_disable.

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 when-to-use guidance is given. The obvious routing question — when to enable versus connect or disconnect a connection — is left entirely to inference, and the natural counterpart tool integrations_disable is never mentioned.

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