Workflows: integration add

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the mutation semantics are covered structurally. The description adds only the 'named flags, no params JSON' convenience and provider examples; it omits any note on auth/credential needs or that it modifies an existing workflow.

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?

A single front-loaded sentence with zero filler, and the core action leads. It is efficient, though for a 15-parameter tool the extreme brevity edges toward underspecification rather than true conciseness.

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 15-parameter mutation tool with no output schema, the description is far too thin: it does not cover credential-source variants, the required provider/operation inputs, or what happens on success. An agent gets almost no help beyond the schema it must already read.

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 100%, so all 15 parameters are already documented in the schema, establishing the baseline of 3. The description alludes to the input/inputs/model parameters via 'named flags' but adds no syntax or format detail beyond what the schema provides.

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 and resource ('Add an Integration step') and grounds it with concrete provider examples (Claude, OpenAI, Slack), so an agent knows exactly the operation type. However, it never distinguishes itself from the closely-named sibling workflows_step_add, leaving the reader to infer that this variant is integration-specific.

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?

There is no when-to-use guidance, no prerequisites (e.g. that provider and operation are required), and no reference to the obvious alternative workflows_step_add. The parenthetical about avoiding hand-written JSON is a value prop, not routing guidance.

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