Integrations: execute

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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false): it warns the call is live, may incur the provider's charges, uses the project's first enabled connection, is limited to claude, and errors for other providers. The charge warning and first-connection behavior are exactly the kind of risk context annotations cannot convey.

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 dense sentences, front-loaded with the core action and ending with the return format. The provider-specific caveat is packed in but every clause carries information; only marginal tightening is possible.

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 live, charge-incurring, open-world call with no output schema, it covers the essentials: input formats, provider limitation, cost warning, connection selection, and return type. It lacks detail on error shapes other than the non-claude case and any timeout/rate-limit 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 meaning by explaining the two input styles (key=value pairs vs. a JSON object) and enumerating the claude operation's inputs (prompt, system_prompt, model, max_tokens). It does not document how to discover non-claude operation keys beyond pointing at 'integrations get'.

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 ('Run an operation on a connected provider') and immediately scopes it to a live call against the first enabled connection. It distinguishes itself from siblings like integrations_test, integrations_get, and workflows_integration_add by naming the workflow route explicitly.

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 a clear when-not and alternative: only the claude provider runs here, and other providers 'return an error, so use them in workflow steps via workflows_integration_add.' It does not contrast with other integration siblings (integrations_test, integrations_get), but the primary routing decision is spelled out.

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